git-security-checks
Installation
SKILL.md
Git Security Checks
When to Use This Skill
| Use this skill when... | Use the alternative when... |
|---|---|
Running gitleaks to scan for secrets before committing |
Use git-commit-workflow for general staging and commit-message conventions |
Configuring .gitleaks.toml allowlists and pre-commit integration |
Use git-maintain for git fsck integrity checks rather than secret scanning |
| Validating that no credentials leak into a PR | Use git-fix-pr when CI gitleaks scans fail and you need to fix them on branch |
| Setting up pre-commit hooks for credential scanning | Use release-please-protection to detect manual edits to release-managed files |
Expert guidance for pre-commit security validation and secret detection using gitleaks and pre-commit hooks.
Core Expertise
- gitleaks: Scan for hardcoded secrets and credentials using regex + entropy analysis
- Pre-commit Hooks: Automated security validation before commits
- Declarative Allowlisting: Manage false positives via
.gitleaks.tomlconfiguration - Security-First Workflow: Prevent credential leaks before they happen