Secrets Scanner
When to use
This skill covers three scenarios: an active leak (incident), preventive scanning, and setting up prevention. The action order differs sharply per scenario, so phase 1 explicitly asks which one you're doing.
Triggers:
- "I think I accidentally committed a key", "this token looks like it's leaking", "check whether there are secrets in the repo".
- A PR touches files like
.env,.env.*,config/*.yaml,docker-compose*.yml,helm/values*.yaml,*.pem, `*
[Description truncada. Veja o README completo no GitHub.]