Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From stdd-agents
Use when running pre-commit hooks manually (e.g. before committing or after implementing). This project uses prek, not pre-commit. Defines the correct commands for running hooks.
npx claudepluginhub craigtkhill/stdd-agents --plugin stdd-agentsHow this skill is triggered — by the user, by Claude, or both
Slash command
/stdd-agents:pre-commit-hooksThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This project uses **prek** as the pre-commit hook runner. Do NOT use `pre-commit run` — always use `prek run`.
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
This project uses prek as the pre-commit hook runner. Do NOT use pre-commit run — always use prek run.
Run all hooks across all files:
prek run --all-files
Run hooks on specific files:
prek run --files path/to/file.rs
Run hooks on files changed since last commit:
prek run --last-commit
Always run prek run --all-files after implementing code and before committing, as part of the STDD workflow:
prek run --all-files ← hereOn a fresh checkout, install the git hooks with:
just setup
Which runs:
prek install
prek install --hook-type commit-msg
prek install --hook-type pre-push
Hooks are split across two stages:
prek install): formatting, linting, style checks — run on every commitprek install --hook-type pre-push): heavier checks like cargo deny — run on push