iterative review

Engineering Community

Skill notes

Usage

Break-glass override. For hotfixes when a real review would block a critical merge, --override tells review-coordinator to skip Steps 2–6, write a single APPROVE iteration to state with "override": "break-glass", and exit. The override is tracked in review-state-<branch>.json for retrospective analysis. The next iteration without --override runs the full review normally. Equivalent: a comment containing break glass in the user's prompt to the skill triggers the same path. Use sparingly; review-coordinator's verdict rubric already biases toward APPROVE for legitimate cases.

State Files

All state lives in .claude/state/ (gitignored). Per branch: File · Purpose · Lifecycle plan-<branch>.md · The current implementation plan · Rewritten on --plan-only review-context-<branch>.md · Shared context every sub-reviewer reads · Rewritten by coordinator each iteration review-state-<branch>.json · Append-only findings history · Coordinator appends, never rewrites

Phase 1: Plan

If .claude/state/plan-<branch>.md doesn't exist, or --plan-only was passed: Read the ticket / user intent from the conversation context Spawn the architect agent with prompt: "Produce an implementation plan for the current task. Identify changed surfaces, risks, and the minimum coherent scope. Output in markdown with sections: Goal, Changes, Risks, Out-of-scope." Write architect's output to .claude/state/plan-<branch>.md

Phase 2: Implement

Make the changes per the plan. This phase runs as the main agent (you), not a sub-agent — the user sees code as it lands. Apply project rules from .claude/rules/ automatically. Run {{TEST_COMMAND}} and {{FORMAT_COMMAND}} as you go. If --review-only, skip this phase.

Phase 3: Review (Coordinator)

Spawn the review-coordinator agent: The coordinator handles all sub-agent orchestration — do not spawn individual reviewers from this skill.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Plan

If `.claude/state/plan-<branch>.md` doesn't exist, or `--plan-only` was passed: Read the ticket / user intent from the conversation context Spawn the `architect` agent with prompt: "Produce an implementation plan for the current task. Identify changed surfaces, risks, and the minimum coherent scope. Output in markdown with sections: Goal, Changes, Risks, Out-of-scope." Write architect's output to `.claude/state/plan-<branch>.md`

02
Phase 2: Implement

Make the changes per the plan. This phase runs as the main agent (you), not a sub-agent — the user sees code as it lands. Apply project rules from `.claude/rules/` automatically. Run `{{TEST_COMMAND}}` and `{{FORMAT_COMMAND}}` as you go. If `--review-only`, skip this phase.

03
Phase 3: Review (Coordinator)

Spawn the `review-coordinator` agent: The coordinator handles all sub-agent orchestration — do not spawn individual reviewers from this skill.

04
Phase 4: Surface Verdict and Next Action

Read the coordinator's report. Show the user: Tier and agents used (so they know what was checked) Findings grouped by severity (collapsed for nits) Verdict (APPROVE / APPROVE_WITH_NOTES / REQUEST_CHANGES / NEEDS_DISCUSSION) Suggested next action:

05
Phase 5: Iterate

When the user runs `/iterative-review` again after making changes: Coordinator reads prior `review-state-<branch>.json` Findings that no longer reproduce → marked `fixed`, shown in "Resolved" section Findings still present → carried forward New issues introduced by the fixes → flagged as new

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.