PR Flow

Take an issue through to a PR in this repo and close it out after merge. Use when asked to open, create or submit a PR; when naming a branch; when signing off commits or repairing a missing Signed-off-by; when recording client evidence for a PR; when requesting a Copilot review, answering its comments or deciding whether to run another round; or when closing out after a merge.

92,088 stars 11,978 forksGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add modelcontextprotocol/servers --skill pr-flow
Manual install
git clone --depth 1 https://github.com/modelcontextprotocol/servers.git /tmp/servers
mkdir -p ~/.claude/skills
cp -r /tmp/servers/.claude/skills/pr-flow ~/.claude/skills/pr-flow

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# PR flow

The rules this procedure carries out live in [`AGENTS.md`](../../../AGENTS.md)
(**Contributing**, **Issue-driven work style**, **Responding to code reviews**,
**Waiting on long-running work**). Board mechanics, including every board ID,
are in `/board-ops`; creating a missing issue is `/issue-create`. This file names
board columns and nothing else.

**Pull requests against this repo are opened by the maintainers only.** Write
access is not authorization to open one. Anyone else files a detailed issue
(`/issue-create`) and a maintainer takes it from there.

## 1. Start from an issue

**Every PR closes an issue.** A PR with no linked issue has no board card, so
the work is invisible to the board. If there is no issue yet, create one first
with `/issue-create`; never open the PR and backfill.

**Read the issue in full, every comment included.** Scope changes, maintainer
decisions and "not this, that" corrections are usually in the comments, not the
body:

```sh
gh issue view <N> --repo modelcontextprotocol/servers --comments
```

Then assign it to yourself and move its card to **In Progress** (the
move-a-card recipe in `/board-ops`):

```sh
gh issue edit <N> --repo modelcontextprotocol/servers --add-assignee @me
```

## 2. Branch

`v2/<type>/<N>-<slug>`, cut from **`origin/v2/main`** into a **new git
worktree**, never by switching branches in the primary checkout. The rule, and
the check that this session's own instructions are current, is `AGENTS.md`
Read the full skill on GitHub

Details

Skill name
pr-flow
Path
.claude/skills/pr-flow/SKILL.md
Repo updated
18 November 2026

FAQ

What does the PR Flow skill do?

Take an issue through to a PR in this repo and close it out after merge. Use when asked to open, create or submit a PR; when naming a branch; when signing off commits or repairing a missing Signed-off-by; when recording client evidence for a PR; when requesting a Copilot review, answering its comments or deciding whether to run another round; or when closing out after a merge.

How do I install the PR Flow skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add modelcontextprotocol/servers --skill pr-flow. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is PR Flow popular?

It lives in modelcontextprotocol/servers, which has 92,088 GitHub stars and 11,978 forks, and is included in 1 curated skill list.

Related skills

Board Ops

92k

modelcontextprotocol/servers

gh recipes for the Servers V2 project board (#43): add an issue's card, move its Status, set or change its Priority, delete a card, and recover from a deleted single-select option. Use when moving a card between columns; when setting Status or Priority; when an option ID is rejected; before editing a board field's options; or when cards lost their Status or Priority.

OtherIn 1 list12k

Client Smoke

92k

modelcontextprotocol/servers

Drive a locally built server with a real client: the Inspector CLI (scripted), the Inspector web UI (through Playwright) and an LLM client. Use when smoke-testing a server change; when calling a tool, reading a resource or getting a prompt from the command line; when choosing a protocol era; or when the Inspector CLI will not connect to, or misreads, a server command.

Testing & QAIn 1 list12k

Issue Create

92k

modelcontextprotocol/servers

Create a tracked issue in this repo end to end — duplicate check, v2 label, type label, server-scope label, milestone, board card, Status and Priority. Use when asked to file, create, open or raise an issue; when picking its labels or its milestone; when checking whether one already exists; or when work discovered mid-task needs an issue of its own.

Skill & Plugin AuthoringIn 1 list12k

Release

92k

modelcontextprotocol/servers

Cut a milestone release: the release issue, the preparation PRs on v2/main (audit, changesets Version Packages, Python CalVer), the pure v2/main to main merge PR with its release ledger, then the GitHub Release a maintainer publishes.

Git & Code ReviewIn 1 list12k

Local Dev

92k

modelcontextprotocol/servers

Install, build and run a server from this checkout. Use when starting a server locally over stdio, SSE or Streamable HTTP; when pointing npx, uvx or an MCP client config at the local build; when a running server still shows old code, or dist is missing; when setting up a git worktree; or when adding an overrides pin.

Git & Code ReviewIn 1 list12k

Repo Guidance

31k

ComposioHQ/composio

Navigate the Composio SDK monorepo, branch and PR workflow, repo layout, generated-file boundaries, changesets, and shared maintenance rules. Use when work spans multiple packages, when deciding where code belongs, when preparing a PR, or when the user asks about repository conventions rather than a specific SDK implementation.

Git & Code ReviewIn 1 list5k

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.