dev-loop-review
Staff review for /dev-loop. Spawn code-reviewer on the diff, write verdict.json. Use after verify is green, before the PR.
- License 许可
- MIT
- 最近更新
- 2026-09-02
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- dev-loop-review
- description
- Staff review for /dev-loop. Spawn code-reviewer on the diff, write verdict.json. Use after verify is green, before the PR.
03 SKILL.md 正文
Dev-loop review
- Spawn
code-reviewerongit diffvs the default branch. Reuseverify.log; do not re-run the full suite here (the conductor re-verifies after a pass). - The reviewer must cover: real bugs/authz/secrets, silent failures (swallowed errors, fake fallbacks), test gaps on new branches, type/invariant holes, and comment rot in the diff. Confidence ≥ 80 only.
- Write
verdict.jsonin the run dir:
{"verdict": "good", "summary": "one sentence", "risks": []}
verdict one of: excellent, good, good-with-risks, needs_improvement, blocker.
excellent/good → ship. Anything else → writer (caps in config). After cap, still ship with risks in the PR.
- Write
SESSION_DONEandSTAGE_DONE. If the verdict shows a durable convention miss (not a one-off bug), loadagent-memoryand update one relevant file; do not invent ADRs or always-on rules.
Do not commit. Do not open a PR. Do not spawn extra marketplace agents.
For durable convention misses, put items in verdict.json metadata[] (target/text[/path/globs/reason]). Conductor auto-applies when agent_memory.auto_apply is true; do not invent ADRs or always-on rules.
04 同仓库更多 Skills
verify-before-done
Use before claiming work is complete, fixed, or passing, and before commit or PR. Run the proof command in this turn.
token-playbook
Token budget for Claude Code. Use when shrinking CLAUDE.md, choosing skills vs rules vs MCP, compressing tool output, or cutting always-on context.
test-writer
Write failing tests from a technical spec and public contracts only. Use in /dev-loop test-writer stage. Do not read implementation sources or write production code.
tdd
Use when implementing a feature or bugfix, before writing production code. Test first, watch it fail, then implement. Vertical slices at public seams.
systematic-debugging
Use when hitting a bug, test failure, or unexpected behavior, before proposing a fix. Find root cause first.
story-spec
Turn a Jira story into a technical spec via grill. Use in the spec stage of /dev-loop. Do not implement.