Secret Scanning

Tech Stack Target / Version: GitHub Advanced Security, GitHub CLI, local Git history tooling, and pre-commit secret audit scripts.

Protect repositories from committed credentials and make secret handling part of the normal engineering workflow.

• Leverage native parallel subagent dispatch and 200k+ context windows where available.

When to Use

Use symptom -> action triggers: when one matches, apply this skill and verify with the protocol below.

• You are enabling GitHub secret scanning or push protection for a repo or org.
• A push was blocked because a secret was detected.
• You need to define or review custom secret patterns and exclusions.
• You want a local pre-commit secret check before pushing code.
• You are triaging secret alerts and planning remediation.