Address Code Review

Work through code review comments with the user, one comment at a time. Never present multiple comments at once.

Critical rule: Do not make any code changes — not a single edit — until every comment has been triaged with the user. Triage and implementation are strictly separate phases. Implementation only begins after the final comment has been discussed and a decision recorded.

Auto-mode does not override this. Auto-mode tells you to minimize interruptions and prefer action; this skill tells you to stop and wait for a decision after every single comment. When the two conflict, this skill wins — the user invoked it specifically to slow you down. Wait for the user's reply on each comment before moving to the next, even if it feels like you're stalling.

Input sources

Comments may come from:

1. review.jsonl - A JSONL file at the repo root. Each line is a JSON object: {"base":"<sha>","comment":"...","compare":"<sha>","endLine":45,"file":"main.go","startLine":42}
2. GitHub PR - Fetch inline and general comments using gh api
3. Document in the repo - Parse whatever markdown structure is found
4. Conversation - Comments given directly by the user

When no explicit source is specified, check for review.jsonl at the repo root first. If it exists, use it.