GitHub Address Comments
Workflow
- Fetch PR review comments and unresolved threads. Prefer thread-level state when available so resolved items are not reworked.
- Classify each comment as actionable, already addressed, question-only, stale, or blocked.
- For actionable items, inspect the surrounding source and caller path before editing.
- Apply the smallest edits needed to satisfy the comment. Keep unrelated files and user-owned changes untouched.
- Re-read the modified path and verify the reviewer concern is actually handled.
- Follow
harness/skills/validate/SKILL.mdwhen the edit affects code, build, or tests. - Summarize each comment with status: fixed, already addressed, needs user decision, or cannot verify.
Guardrails
- Do not resolve or reply to review threads unless explicitly asked.
- Do not batch unrelated review comments into broad refactors.
- Preserve staged-only workflows. If files are already staged, inspect staged and unstaged diffs separately before committing.
- For docs-only comments, avoid triggering builds unless the changed docs affect generated commands or scripts.