Security Vulnerability: py-bugger CLI Tool Fails to Warn Users About Project Secrets

A security vulnerability has been identified in the py-bugger command-line tool, where the software provides no warning before operating on projects containing sensitive data such as API keys and passwords. This oversight occurs during execution, specifically when py-bugger processes files, leaving developers unaware that their secrets could be exposed or inadvertently modified by the tool's operations.

The issue is pinpointed in the `src/py_bugger/cli/config.py` file, lines 17-27. The tool currently lacks any mechanism to detect common secret-bearing files like `.env`, `secrets.py`, or `config.py` files containing credentials. The vulnerability is categorized as a 'Minor' security flaw, but it represents a tangible risk for developers working with private repositories or sensitive configurations, as running py-bugger could silently interact with these files.

The proposed fix is to implement a pre-execution check for these common secret file patterns and display a clear warning to the user before any code modification begins. This would alert developers to the presence of potential secrets, allowing them to abort or take precautions. Without this safeguard, the tool poses a subtle but persistent security risk in development workflows, especially in automated or scripted environments where manual oversight is limited.