mcpField
P
pull-requests

pull-requests

github.com/gannonhDevelopment248 installsUpdated 8w ago
Repository

About pull-requests

pull-requests is a skill for managing the PR lifecycle, selecting a workflow based on user intent and the current PR state. It covers creation, review, handling feedback, and merging through dedicated procedures.

Key features

  1. 01Select a PR workflow by intent
  2. 02Create and push PRs
  3. 03Review code against a PR diff
  4. 04Address existing review comments
  5. 05Run final checks and merge

Use cases

  1. 01Submit feature branch changes for review
  2. 02Review code quality on an open PR
  3. 03Fix and respond to review feedback
  4. 04Merge a PR after final checks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gannonh/skills --skill pull-requests

After installing, type/pull-requestsin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
addressing-workflow.md
code-reviewer-instructions.md
code-simplifier-instructions.md
comment-analyzer-instructions.md
creating-workflow.md
failure-finder-instructions.md
merging-workflow.md
pr-test-analyzer-instructions.md
reviewing-workflow.md
type-design-analyzer-instructions.md
scripts/
create_pr_safe.py
fetch_comments.py

Details

From the project README

Pull Request Workflows

This skill handles the complete PR lifecycle. Based on context and user intent, follow the appropriate workflow.

Context

  • Current git status: !git status
  • Current branch: !git branch --show-current
  • PR state (if exists): !GH_PAGER= gh pr view --json number,title,state 2>/dev/null || echo "No PR for current branch"
  • Arguments: $ARGUMENTS

Workflow Selection

Determine which workflow to use based on context:

Use Creating Workflow when:
  • User asks to "create a PR", "open a PR", "push for review"
  • On a feature branch with uncommitted or unpushed changes
  • No PR exists for the current branch

→ See ./references/creating-workflow.md

Use Reviewing Workflow when:
  • User asks to "review PR", "check code quality", "run review"
  • PR exists and is open
  • Want a fresh code review against the PR diff using targeted reviewers
  • This workflow does NOT address existing review comments — it runs its own analysis

→ See ./references/reviewing-workflow.md

Use Addressing Workflow when:
  • User asks to "address comments", "fix review feedback", "respond to reviewer"
  • PR exists with unresolved review comments from human reviewers or bots
  • User wants to respond to specific existing feedback without running a fresh review

→ See ./references/addressing-workflow.md

Use Merging Workflow when:
  • User asks to "merge PR", "complete PR", "finalize changes"
  • PR exists, is reviewed, and ready for merge
  • Need to run final CI checks and merge

→ See ./references/merging-workflow.md

Quick Reference

IntentWorkflowKey Actions
"Create PR"CreatingBranch → Commit → Push → <path-to-skill>/scripts/create_pr_safe.py
"Review PR"ReviewingGather context → Fetch diff → Scope & run reviewers → Present findings → Fix
"Address comments"AddressingFetch comments → User selects → Fix → Reply → Push
"Merge PR"MergingCI checks → Confirm ready → gh pr merge → Checkout main

Comments

Markdown supported