feedback-resolutionlisted

# Feedback Resolution Domain skill for systematically addressing PR review comments. ## Iron Law **EVERY FIX TRACES TO A SPECIFIC REVIEW COMMENT OR THE BOY SCOUT RULE. Untraceable changes that fail the proximity test are out-of-context changes.** If you can't point to the review comment or the Boy Scout proximity test that motivated a change, the change doesn't belong in this round. ## Focused Change Principle When addressing feedback, fix what the feedback requires — and apply the Boy Scout Rule to files you're already modifying: - Each feedback fix should be traceable to a specific review comment - Don't add features while addressing feedback - Don't change formatting in files not mentioned in feedback - Boy Scout cleanup in files being modified for feedback is allowed if it passes the proximity test (see `code-quality-principles`) - Boy Scout fixes get separate `improve:` commits, never mixed with feedback fixes ## Feedback Collection Fetch all review feedback: ```bash PR_NUM=$ARGUMENTS REPO=$(gh repo view --json nameWithOwner --jq '.nameWithOwner') # Review comments with file:line context gh api repos/$REPO/pulls/$PR_NUM/comments --jq '.[] | {id: .id, path: .path, line: .line, body: .body, author: .user.login}' # Review summaries and states gh pr view $PR_NUM --json reviews --jq '.reviews[] | {state: .state, body: .body, author: .author.login}' # Root conversation threads (for grouping replies) gh api repos/$REPO/pulls/$PR_NUM/comments --jq '.[] | select(.in_