Menú
Pre-commit gate (fmt + clippy + test) then create a conventional commit with explicit file staging.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Review a pull request or pending changes. Performs a focused code review against the current branch's diff (or staged diff if invoked pre-commit), surfacing correctness bugs, missing tests, style violations, and unclear naming. Use when the user asks to "review this", "review the PR", "code review", or before commits/PRs.
Complete a security review of pending changes on the current branch. Focuses on injection, authn/authz, secrets, SSRF, deserialisation, insecure defaults, and supply-chain risk. Use when the user asks to "security review", "security audit", "check for vulns", or before raising a PR.
Create or update ARCHITECTURE.md with system components, data flows, and ADRs
Format Rust code with rustfmt and report what changed.
Full TDD loop — plan, branch, write code + tests, fmt, clippy, test, review, commit.
View the story board grouped by status, with optional filters
| name | commit |
| description | Pre-commit gate (fmt + clippy + test) then create a conventional commit with explicit file staging. |
The enforcer. Nothing reaches the index without passing the gate.
cargo fmt -- --check
If dirty: run /fmt to apply formatting, then re-stage any files that were already staged.
cargo clippy --all-features --all-targets -- -D warnings
If any warnings/errors are reported: fix them. Do not add #[allow(clippy::...)] suppression unless the lint is a confirmed false positive — and even then, add a comment explaining why. Re-run clippy until it exits 0.
Run /test. Must pass, including the coverage gate. If it fails: halt. Surface the failure and let the user decide.
Run /review against staged changes (git diff --cached).
The
/reviewskill is diff-aware — it picks up staged changes automatically when invoked here.
Handle findings:
[needs-decision]): apply, re-stage the file, then re-run /test.[needs-decision] findings: surface to the user. Do not silently apply.If any fix was applied: loop back to step 1. Max 2 loops, then escalate.
git add <file1> <file2> ...
Never git add -A or git add .. These are denied at the settings level — if Claude tries them, the call will be rejected.
Use git status --short to enumerate what's intended for the commit. If something unintended shows up (e.g. Cargo.lock changes you didn't intend), ask the user.
Format: conventional commits.
<type>(<scope>): <short imperative description>
<optional body — wrap at 72 cols, explain the WHY, not the WHAT>
Types: feat, fix, chore, test, docs, refactor, perf, style, build, ci.
Rules:
Co-Authored-By line — Claude Code attaches one automatically.git commit -m "$(cat <<'EOF'
<message>
EOF
)"
Use a heredoc so multi-line bodies format correctly.
git log -1 --oneline
git status --short
Report: commit hash, subject line, working-tree state. One line each, no padding.
If a pre-commit hook fails: the commit did not happen. Fix the underlying issue, re-stage, and create a new commit. Never --amend after a hook failure — there's nothing to amend.