git-pr-feedback Skill | Agent Skills

Context

Repo: !git remote -v
Current branch: !git branch --show-current
Git status: !git status --porcelain=v2 --branch

Parameters

Parse these parameters from the command (all optional):

| Parameter | Description | |-----------|-------------| | $1 | PR number (if not provided, detect from current branch) | | --commit | Create commit(s) after addressing feedback | | --push | Push changes after committing (implies --commit) |

When to Use This Skill

| Use this skill when... | Use another skill instead when... | |------------------------|----------------------------------| | A PR has reviewer comments to address | CI checks are failing with no review comments -> use git-fix-pr | | You need to systematically work through review feedback | You're creating a new PR -> use git-commit-push-pr | | A reviewer has requested changes | You want to understand PR workflow patterns -> use git-branch-pr-workflow |

Your Task

Review PR workflow results and reviewer comments, then address substantive feedback.

For feedback categorization, decision trees, commit format, and report templates, see REFERENCE.md.

Step 1: Determine PR and Gather All Data

Get PR number from argument or detect from current branch:
```
gh pr view --json number -q '.number'
```

Switch to PR branch if not already on it:

gh pr view $PR --json headRefName -q '.headRefName'
git switch <branch-name>
git pull origin <branch-name>

Parse owner/repo from the git remote URL.

Fetch ALL PR data using the bundled script (single GraphQL query):

bash ${CLAUDE_SKILL_DIR}/scripts/fetch-pr-data.sh <owner> <repo> <pr-number>

For failed checks only, fetch detailed logs:
```
gh run view $RUN_ID --log-failed
```

| Check Status | Action | |--------------|--------| | All passing | Skip to Step 2 | | Failed CI | Get logs with gh run view, may need fixes | | Pending | Note status, focus on comments |

If the GraphQL query fails with a rate limit error, wait 60 seconds and retry once.

Step 2: Analyze Feedback

Categorize all comments from the GraphQL response (see REFERENCE.md for category definitions):

Categorize each comment as Blocking, Substantive, Suggestion, Question, Nitpick, or Resolved
For each actionable comment, note file, line, scope, and dependencies
Create a todo list using TodoWrite with all actionable items

Step 3: Address Feedback

Work through actionable items systematically:

Code review comments: Read relevant code, understand context, implement fix, verify no breakage.

Failed CI checks: Identify failure type (lint/type/test/build), fix locally, run to verify.

Questions/clarifications: Note for PR reply; consider adding code comments for future readers.

Step 4: Commit Changes (if --commit or --push)

Group related fixes into logical commits. See REFERENCE.md for commit message format.

Run pre-commit hooks if configured, then stage any formatter changes.

Step 5: Push Changes (if --push)

git push origin HEAD

Step 6: Summary Report

Provide a summary table of feedback addressed, changes made, and next steps. See REFERENCE.md for report template.

Agentic Optimizations

| Context | Command | |---------|---------| | All PR data (single query) | bash ${CLAUDE_SKILL_DIR}/scripts/fetch-pr-data.sh <owner> <repo> <pr> | | Failed check logs | gh run view $ID --log-failed | | Quick check status (fallback) | gh pr checks $PR --json name,state,conclusion |

Agent Skills: git-pr-feedback

Install this agent skill to your local

Skill Files