AGENT SKILL

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

  1. Spawn code-reviewer on git diff vs the default branch. Reuse verify.log; do not re-run the full suite here (the conductor re-verifies after a pass).
  2. 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.
  3. Write verdict.json in 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.

  1. Write SESSION_DONE and STAGE_DONE. If the verdict shows a durable convention miss (not a one-off bug), load agent-memory and 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