Fix Pr Comments

Step 3: Analyze and Address Each Comment

For each todo item:

1. Evaluate the comment validity: Before implementing changes, critically assess:
   • Does the comment align with best practices and project standards?
   • Is the suggested change technically sound?
   • Could the change introduce bugs or security issues?
   • Is there a better alternative approach?
   • If unsure, discuss with the user before proceeding
2. Read the file: Use the Read tool to examine the code at the specified line
3. Understand the context: Read surrounding code to understand the implementation
4. Analyze the review comment: Determine what change is being requested
5. Propose a solution: Based on the comment, suggest specific code changes
6. Ask for confirmation: Show the user what you plan to change and ask if they approve
7. Implement the fix: Once approved, use the Edit tool to make the changes
8. Mark todo as completed: Update the todo list to track progress using TaskUpdate
9. Move to next comment: Continue until all comments are addressed

Step 4: Summary and Next Steps

After addressing all comments:

1. Summarize what was changed
2. Suggest running tests if applicable
3. Recommend the user to reply to review threads on GitHub
4. Optionally offer to commit the changes
5. Note any comments that were not implemented and explain why (if applicable)

Output Format (Step 1)

The output will show:

• 📁 File path and line number
• 🧵 Thread ID
• 🟢 Original comment (thread starter)
• 💬 Reply comments (indented)

Example Workflow

See examples/sample-output.md for detailed output examples.

Prerequisites

• The current branch must have an associated pull request
• GitHub CLI (gh) must be authenticated
• jq must be installed

Important Notes

• Always read the file before making changes to understand the full context
• Ask for user confirmation before implementing significant changes
• Track progress using TaskCreate, TaskUpdate, and TaskList tools
• If a comment is unclear, ask the user for clarification
• Consider the impact of changes on related code and tests
• Maintain the existing code style and conventions
• Critical thinking required: Not all review comments are correct or appropriate
  • Some comments may be based on misunderstandings or outdated practices
  • Some suggestions may introduce bugs or violate project conventions
  • Always validate the technical soundness of suggestions before implementing
  • If a comment seems questionable, discuss with the user and explain your reasoning
  • It's acceptable to respectfully decline a suggestion if you can justify why it's not appropriate

Error Handling

• If there are no PR comments, inform the user and exit gracefully
• If a file cannot be read, skip that comment and note it in the summary
• If GitHub CLI fails, display the error and suggest troubleshooting steps
• If jq is not installed, provide installation instructions for the user's platform:
  • macOS: brew install jq
  • Ubuntu/Debian: sudo apt-get install jq
  • Other: Visit https://stedolan.github.io/jq/download/
• If GitHub CLI authentication fails, guide user to run gh auth login
• If a comment thread cannot be matched to a file location, skip and note in summary
• If Edit tool fails due to file changes, re-read the file and retry with updated context