← ClaudeAtlas

loop-review-foldlisted

Run the simple review-change/fold-findings loop for an open feature or fix unit. Inspect persisted review evidence first so a previous review resumes with fold-findings instead of reviewing the same candidate again. Unresolved findings go to triage-issue with an immediate-fix instruction; oversized findings become a user-confirmed plan-feature or plan-fix replan with new phases. Triggers: "loop-review-fold", "review and fold this PR", "run the review fold loop".
gtrabanco/agentic-workflow · ★ 21 · Code & Development · score 80
Install: claude install-skill gtrabanco/agentic-workflow
# Review / Fold Loop Run one small state loop over the current feature or fix unit: ```text review-change ── findings ──▶ fold-findings ── changed HEAD ──▶ review-change ▲ │ └──────── current PASS ◀───────┘ └─ unresolved ─▶ triage-issue ``` This skill is a router, not a third review or repair implementation. It reads the durable evidence left by `review-change` and `fold-findings`, chooses the next action, and stops when a user decision or manual phase execution is required. Never merge, create an unrelated issue, or silently discard a finding. ## Turn contract ```text ✓ The feature/fix unit, branch, PR, current HEAD, acceptance, and finding ledger were checked ✓ The first action was selected from persisted evidence: PASS, review-change, or fold-findings ✓ review-change ran only when no current review result required fold-findings first ✓ A successful fold was followed by review-change on the new HEAD ✓ Every unresolved finding is named and routed to triage-issue --prioritize-now ✓ An oversized finding routes to plan-feature or plan-fix, new P<n> phases, and manual user execution ✓ No merge, unrelated issue, acceptance weakening, or silent finding drop occurred ✓ The fixed result and the closing → Next: block are the final output ``` Any unchecked box means the turn is not done. ## When to use Use after `execute-phase` opens the unit PR, or when the user asks to review and fold an open fe