security-check

You can prevent API keys and tokens from leaking in git commits by scanning diffs for known sensitive patterns before they are committed. This Skill blocks sensitive credentials at the pre-commit and pre-push stages to stop leakage in shared repos.

Pre-commit secret scanning works by using bash scripts and Git commands to detect API keys and tokens in the staging area. It identifies sensitive information using defined patterns and blocks the commit or push if leakage is detected.

If secrets were already leaked to shared repositories, you can use optional scripts to reset history with built-in safeguards. This provides safe recovery options to remediate commits that contain secrets after detection.

Yes, you can use bash scripts to scan staging area diffs for sensitive information before committing. Running the security check script in commit mode scans the staged changes to detect API keys and tokens using defined patterns.

Yes, pre-push secret detection reports and logs commits containing secrets for remediation. It scans diffs across pre-commit and pre-push stages to identify sensitive credentials and provides safe recovery options.