mcpField
A
address-pr-comments

address-pr-comments

github.com/gannonhDevelopment236 installsUpdated 8w ago
Repository

About address-pr-comments

address-pr-comments is a skill for finding the open pull request on the current branch and working through its review comments with gh. It guides issue triage, code fixes, checks, commits, pushes, and CI follow-up.

Key features

  1. 01Fetch PR comments and review threads
  2. 02Triage actionable findings
  3. 03Apply and validate code fixes
  4. 04Resolve or reply to review threads
  5. 05Commit, push, and monitor CI

Use cases

  1. 01Address feedback on the current branch's open PR
  2. 02Distinguish valid defects from questions or suggestions
  3. 03Verify fixes and follow up on CI failures

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gannonh/skills --skill address-pr-comments

After installing, type/address-pr-commentsin Claude Code to confirm it loaded.

Bundled filesscripts/fetch_comments.py

Details

From the project README

PR Comment Handler

Guide to find the open PR for the current branch and address its comments with gh CLI. Run all gh commands with elevated network access.

Preflight

  1. Create a structured task list of the following steps
  2. Inform the user of what you are doing

You should endeavor to run this entire workflow autonomously, only engaging the user if issues arise or uncertain how to best proceed.

Step 1: Inspect comments needing attention
  • Run <path-to-skill>/scripts/fetch_comments.py which will print out all the comments and review threads on the PR
Step 2: Enumarate issues identified in comments and review threads
  • Number all the review threads and comments
  • Provide a short summary of each "issue candidate," including any suggested fixes from the reviewer
Step 3: Identify actionable issues to address
  • For each issue candidate, analyze against the codebase to distinguish actionable items from false positives or comments that do not require code changes (for example, questions, suggestions, or style comments).
  • Verify each finding against current code. Plan to fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate.
Step 4: Apply fixes to all actionable issues & resolve/address comments
  • Use TDD when possible: write a failing test that captures the issue, then apply the fix to make the test pass.
  • Resolve or reply to those threads in the GitHub UI as you address them. For comments not addressed, reply to reviewers with your reasoning and ask for any clarification if needed.
Step 5: Run checks, commit and push changes
  • After applying fixes, run the relevant tests and checks locally to confirm the issue is resolved.
  • Summarize the changes made, commit with a clear message referencing the PR and issue numbers, and push the changes to the PR branch.
Step 6: Monitor CI Actions and address any new failures
  • After pushing, monitor the PR's CI checks for any new failures that may arise from the changes.
  • If new failures occur, use the gh-fix-ci skill to analyze the CI logs, identify the root cause, and apply necessary fixes.

Final verification and summary

  • Double check that all comments have been addressed and resolved in the GitHub UI.
  • Summarize the outcome of the comment addressing process, including any remaining open questions or follow-ups needed with reviewers.

Notes:

  • If gh hits auth/rate issues mid-run, prompt the user to re-authenticate with gh auth login, then retry.
  • If sandboxing blocks gh auth status, rerun it with sandbox_permissions=require_escalated.

Comments

Markdown supported