implement-review-loop

Orchestrates a bounded implement, review, and fix loop with objective stop conditions.

Updated Jul 4, 2023
One-click install
npx skills add https://github.com/kohdice/dotfiles --skill implement-review-loop-kohdice
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement-review-loop
Source: https://github.com/kohdice/dotfiles/tree/main/config/agents/skills/implement-review-loop
Command: npx skills add https://github.com/kohdice/dotfiles --skill implement-review-loop-kohdice

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Iterating between implementation and code review often turns into an unbounded loop where LLM reviewers never run out of advisory findings, causing code to be shaped to please reviewers instead of users. This Skill gates only on high-severity blocking findings and enforces a hard cap on fix rounds, so implementation-review cycles terminate with objective stop conditions. ## Core Features & Use Cases - Bounded loop orchestration: Composes the implement and local-review skills by reference, adding only loop control, a findings ledger for cross-round recurrence detection, and a final report. - Severity-based gating: Only high-severity findings block the loop (medium only on explicit user request); advisory findings pass through to the final report untouched. - Fresh reviewers and evidence: Every review round dispatches new reviewer sub-agents, and every fix round ends with a parent-run full test suite before the next review. - Use Case: Ask the agent to implement a new feature and iterate until review findings are resolved; the loop implements, reviews, fixes blocking findings across at most 2 fix rounds, then reports remaining findings and suggests committing via the git-commit skill. ## Quick Start Use the implement-review-loop skill to implement this feature and iterate until the review findings are resolved.

Frequently Asked Questions about implement-review-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a feature and iterate on code review findings automatically?▼

Request implementation and review iteration in the same prompt. The loop runs the implement skill's workflow, dispatches fresh reviewer sub-agents, fixes only high-severity blocking findings, and repeats until no blocking findings remain or the fix-round cap is reached.

When should I use an implement-review loop instead of separate implement and review steps?▼

Use it only when implementation and review iteration are requested together, such as taking a TDD plan to review-clean in one go. For implementation-only or review-only requests, the standalone implement or local-review skills apply instead.

How many fix rounds does the review loop allow before stopping?▼

The default cap is 2 fix rounds, extended to 3 only on explicit user request, and limited to 1 in inline fallback mode. Reaching the cap is a normal exit that lists remaining blocking findings for the user to decide.

Does the review loop fix all findings reported by reviewers?▼

No. Only high-severity findings block the loop and get fixed; medium severity counts only if the user requested a stricter gate upfront. Advisory and lower-severity findings pass through to the final report untouched, since auto-fixing them optimizes for the reviewer rather than the user.

What happens when a fixed finding recurs in a later review round?▼

The loop stops immediately and reports the recurrence, because mechanical repetition will not resolve what a targeted fix could not. A findings ledger tracks each blocking finding by path, lens, and defect summary across rounds to detect recurrence.

Does the implement-review loop commit changes to git automatically?▼

No. Neither the parent nor any sub-agent commits, pushes, stashes, or changes branches. The final report suggests committing via the git-commit skill, potentially one commit per phase, and leaves the decision to the user.