pr-review-workflow
✓CleanUse when addressing PR review feedback, re-requesting reviews, handling GitHub review bot re-reviews (Codex, Copilot), or managing GitHub notifications. Do not use for creating new PRs or general development.
Install Command
npx skills add metyatech/skill-pr-review-workflowSKILL.md
---
name: pr-review-workflow
description: Use when addressing PR review feedback, re-requesting reviews, handling GitHub review bot re-reviews (Codex, Copilot), or managing GitHub notifications. Do not use for creating new PRs or general development.
---
# PR review feedback workflow
## Addressing review feedback
- After addressing PR review feedback, resolve the corresponding review thread(s) before concluding; if you lack permission, state it explicitly.
- Before re-requesting review after addressing feedback, run the relevant verification suite and summarize results (commands + outcomes) in the PR comment/description.
## Re-requesting reviews
- After pushing fixes for PR review feedback, re-request review only from reviewer(s) who posted the addressed feedback in the current round.
- Do not re-request review from reviewers (including AI reviewers) who did not post addressed feedback, or who already indicated no actionable issues.
- If no applicable reviewer remains, ask who should review next.
## AI review bot re-review
When Codex and/or Copilot review bots are configured for the repo, trigger re-review only for the bot(s) that posted addressed feedback.
- For Codex re-review (only when applicable): comment `@codex review` on the PR.
- For Copilot re-review (only when applicable): use the GitHub API to remove and re-request the bot reviewer `copilot-pull-request-reviewer[bot]` (do not rely on UI-based reviewer assignment).
- Remove: `DELETE /repos/{owner}/{repo}/pulls/{pr}/requested_reviewers` with body `{"reviewers":["copilot-pull-request-reviewer[bot]"]}`
- Add: `POST /repos/{owner}/{repo}/pulls/{pr}/requested_reviewers` with body `{"reviewers":["copilot-pull-request-reviewer[bot]"]}`
## GitHub notification management
- Use `DELETE /notifications/threads/{id}` (HTTP 204) to mark notifications as **done** (removes from inbox/moves to Done tab).
- Do NOT use `PATCH /notifications/threads/{id}` (marks as read but leaves in inbox).
- After processing notifications, bulk-delete any remaining read-but-not-done notifications with the same DELETE API.
## Post-merge cleanup
- After completing a PR, merge it, sync the target branch, and delete the PR branch locally and remotely.
Similar Skills
PRD-first feature development workflow that generates a PRD file from a reference template, captures requirements, business flow, clarification questions, and test plans, then waits for user confirmation before implementation. Use when users ask to design or implement new features, change product behavior, request a PRD-driven process, or ask for a greenfield feature that is complex and has no existing base (plan before action).
npx skills add LaiTszKin/develop-new-featuresUse when preparing a release, publishing a package, bumping a version, or configuring public repository metadata. Also use when verifying a published package. Do not use for general development or non-release tasks.
npx skills add metyatech/skill-release-publishGuide the agent to submit code changes or prepare a release. Use when the user asks to commit, submit, push, tag, or release changes, or says æ交/éåº/æ交è®æ´. Default to a commit+push only workflow when the user does not explicitly request versioning. Use release workflow only when the user asks for version/tag/release work.
npx skills add LaiTszKin/submit-changesUse when reviewing an agent's plan, work output, or completion claim on behalf of the user. Evaluates against established rules, known error patterns, and quality standards. Do not use for direct implementation work.
npx skills add metyatech/skill-user-proxy