Pre-commit scanning and pre-launch audits for Claude Code. Catches secrets, personal data, hardcoded paths, and .env files before they reach git history.
/plugin install developer-guard@AhmedHamadto/developer-guard
Two-layer system that blocks sensitive content from reaching git history:
Layer 1: Fast Hook (automatic, ~200ms, zero tokens)
- Regex scan of staged files for API keys, tokens, private keys
- Blocks personal/company references, hardcoded user paths, .env files
- Runs automatically on every
git commitvia PreToolUse hook
Layer 2: Smart Skill (invoke /pre-commit-review)
- Contextual review of the staged diff using Claude
- Catches non-standard secrets, internal project references, sensitive business logic
- Recognizes false positives (example keys in docs, placeholder paths)
Four-step audit orchestrated by /pre-launch-audit:
/repo-scan— Secrets, PII, hardcoded paths, attribution gaps (8 categories)/legal-audit— License compliance, IP risks, trademark concerns (6 categories)/first-run-audit— First-time user experience simulation (8 categories)/launch-ready— README, metadata, contributing guide, professional polish (7 categories)
Produces a single GO/NO-GO launch readiness report.
| Command | What It Does |
|---|---|
/pre-commit-review |
Contextual review of staged changes |
/repo-scan |
Full repository scan for sensitive content |
/legal-audit |
Legal, IP, and attribution audit |
/pre-launch-audit |
All four audits in sequence with consolidated report |
Pairs with software-forge for full software development lifecycle — design, implementation, security, and review phases.
MIT