dev-review

Automate code review gates by serving a local static UI that organizes per-commit cards after phase commits. This browser-based workflow captures per-card feedback and routes non-approved changes back into the worktree for rework.

Yes, persist iterative code review history by storing artifacts like review-data.json, feedback.json, and review-history.json under plans/{task_slug}/dev-review. This supports multi-round review cycles and auditability while preserving previously approved cards.

A browser-based developer review workflow walks reviewers through Overview to per-commit cards to a Final preview. It captures statuses like approved, needs-change, question, or out-of-scope, and optionally dispatches an agent for rework.

Yes, you need a deterministic review-data generator and a static server to serve the UI. The workflow also requires well-formed plan_signature, task_head_sha, and available_agents to properly drive the automated review process.

Handle out-of-scope and needs-change feedback by capturing the status per commit card in the browser UI. The workflow then routes these non-approved changes back into the runner's worktree for rework, Q&A, or out-of-scope records.

Yes, dev-review preserves previously approved cards when rounds continue. It re-generates deterministic review data using a helper script and serves the local static UI, enabling iterative feedback loops without losing prior approvals.