1. Read the thread ID, file path, line number, and all comments
2. Read the relevant file and surrounding context
3. Understand what change is being requested
4. Categorize the feedback:
   • Actionable: Code change, fix, or improvement needed
   • Question: Clarification needed - respond with explanation
   • Discussion: Opinion/preference - assess if change improves code
   • Already addressed: Change was made but thread not resolved
   • Won't fix: Explain why the current approach is preferred
   • Follow-up issue: Valid improvement but out of scope - create linked issue

1. Make the change (if actionable):
   • Read the file(s) that need changes
   • Make the requested changes using Edit tool
   • Run the project's lint/format/check commands (see CLAUDE.md or package.json for scripts)
2. Commit the change (if code was modified):
   bash

   git add <files>
   git commit -m "fix: Address PR feedback - <brief description>"

3. Reply DIRECTLY to that specific thread using GraphQL:
   bash

   # Reply to a review thread (NOT a PR comment!)
   gh api graphql -f query='
   mutation {
     addPullRequestReviewThreadReply(input: {
       pullRequestReviewThreadId: "<THREAD_ID>"
       body: "<response>"
     }) {
       comment {
         id
       }
     }
   }'

   Alternative using REST API (reply to the first comment in the thread):
   bash

   gh api repos/{owner}/{repo}/pulls/<PR_NUMBER>/comments/<COMMENT_ID>/replies \
     -X POST \
     -f body="<response>"

4. Move to the next thread and repeat

• Actionable: "Fixed in commit

  <sha>

  . <brief explanation of the change>"
• Question: "<answer to the question with code references if helpful>"
• Discussion: "Good point. <explanation of decision - either made the change or explained why not>"
• Already addressed: "This was addressed in commit

  <sha>

  . <brief explanation>"
• Won't fix: "Keeping the current approach because <reason>. Happy to discuss further."
• Follow-up issue: "Created #<issue_number> to track this. <brief explanation of why it's out of scope>"

<quote the reviewer's comment>

• PR: #<PR_NUMBER>
• Review comment: <link to the comment>"

undefined

• Number of feedback items addressed
• Commits created (list each)
• Follow-up issues created (with links)
• Any items that need human review or decision

1. Use GraphQL for thread discovery: The REST API (

   /pulls/{}/comments

   ) does NOT show resolution status. Always use the GraphQL query to find unresolved threads.
2. Reply to threads individually:
   • DO NOT post one collective comment addressing all feedback
   • DO reply directly to each thread as you address it
   • This keeps discussions organized and allows threads to be resolved
3. Reply immediately after addressing: Don't wait until the end to reply. Address thread → reply → move to next thread.
4. Be thorough: Address ALL unresolved feedback, don't skip items
5. Be specific: Reference exact commits, line numbers, and code in responses
6. Test changes: Run checks and tests before committing
7. Granular commits: One commit per logical change for easy review
8. Create follow-up issues: When valid feedback is out of scope, create a linked issue rather than ignoring or scope-creeping the PR