asapp-resolve-review-issues

To resolve code review issues in a TODO.md file, this Skill processes nested review bullets one at a time, using subagents to investigate and propose fixes, requiring your approval before applying edits and committing each resolved issue separately.

The best way to commit code review follow-ups without scope creep is task-scoped issue resolution, which isolates each fix to a single review bullet and commits it independently to maintain strict auditability.

No, you cannot apply multiple review fixes in a single commit. The workflow enforces strict one-issue orchestration, requiring exploration, user approval, and exactly one commit per resolved review issue.

Subagents handle issue triage by delegating context gathering and implementation tasks, keeping the main orchestration clean while exploring and repairing code for logged review notes.

Yes, you must approve all proposed file changes before they are applied. Safe implementation gates require explicit user approval before any edits are made to resolve the current review issue.

You should not use this automated commit workflow if your review notes are not already logged beneath a TODO.md task, as it requires pre-documented issue bullets to process issues sequentially.