Keep leaked secrets out of your GitHub repos.
What it does
Guides GitHub secret-protection setup and exposed-credential remediation so users can prevent and address secret leaks.
When to use it
Use when configuring secret scanning or push protection, defining patterns, resolving blocked pushes, managing alerts, or scanning changes before committing.
How to use it
Give it a repository and a secret-protection request; it guides configuration and remediation in GitHub.
What you provide
- An existing project
Uses
Good to know
- cannot be undone: exposed credentials
What you need · 1
Repository protection configuration requires GitHub access as a repository admin, organization owner, or security manager.
Access · 3
This skill
exposed credentials
Revokes and replaces exposed credentials (irreversible)
GitHub
Configures GitHub secret protection
advanced-security
Installs the Advanced Security plugin