Menu
Use when a pull request already has review feedback that needs triage, code changes, verification, and clear replies back to reviewers.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | respond-pr |
| version | 1.0.0 |
| description | Use when a pull request already has review feedback that needs triage, code changes, verification, and clear replies back to reviewers. |
| activation | {"patterns":["respond.*review","address.*review"],"keywords":["review","feedback","pr"],"max_context_tokens":2500} |
gh auth status succeedsAGENTS.md defines the quality gate for the projectgh pr view --json number,title,headRefName.AGENTS.md.Collect:
Record author, location, body, thread grouping, and whether the comment is resolved.
Group overlapping comments into one action item per concern.
Present a table with:
Wait for confirmation before changing code.
For each approved fix:
AGENTS.md.Present:
Use when a GitHub issue should be handled end-to-end, including issue analysis, code changes, tests, verification, and an optional commit.
Use when working with GitHub repositories, issues, pull requests, branches, or commits and the task needs authenticated repository operations or GitHub metadata.
Use when a task needs a written execution plan with explicit steps, risks, verification, and user approval before implementation starts.
Use when a pull request needs one coordinated workflow covering review state, fixes, checks, branch updates, and merge readiness.
Use when deciding whether a change is ready to merge and a concise cross-language checklist is more useful than a full narrative review.
Use when a pull request needs a serious pre-merge review covering correctness, edge cases, security, tests, documentation, and architecture.