Menu
Pre-commit verification: security scan, quality gates, auto-fix before committing.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Karpathy-inspired guidelines: Think before coding, Simplicity first, Surgical changes, Goal-driven execution
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Write an actionable markdown plan before implementation. Bite-sized tasks, exact paths, complete code.
Write clear Conventional Commits. Imperative subject, explain why not what, one logical change per commit.
Optimize based on measurement, never guesswork. Profile first, fix the real bottleneck, verify the win.
Refactor code without changing behavior. Small steps, green tests after every change, no mixing with feature work.
| name | requesting-code-review |
| description | Pre-commit verification: security scan, quality gates, auto-fix before committing. |
Core principle: No agent should verify its own work. Fresh context finds what you miss.
git commit or git pushgit diff --staged
If empty, try git diff then git diff HEAD~1 HEAD. If still empty, nothing to verify.
# Hardcoded secrets
git diff --staged | grep "^+" | grep -iE "(api_key|secret|password|token|passwd)\s*=\s*['\"][^'\"]{6,}['\"]"
# Shell injection risk
git diff --staged | grep "^+" | grep -E "os\.system\(|exec\.Command.*\+"
# Unsafe operations
git diff --staged | grep "^+" | grep -E "io/ioutil\.ReadFile|os\.Chmod\(.*0777"
Any match is a blocking concern.
go test ./... -count=1
Only new failures block the commit. If tests already fail, note them but don't block.
# Go
go vet ./...
# Also check formatting
gofmt -l .
Any go vet warnings in changed code must be fixed.
fmt.Println("DEBUG"), log.Print)For each issue found, apply the minimal fix with edit, then re-run tests.
Summarize: what was checked, issues found, issues fixed, remaining concerns.