Table of Contents generated with DocToc

• PR management skill family
  • Install & first runs
    • Before the first run
    • Works well with
    • Try these first
  • Skills
  • Cross-references

Scope. Works on any project, ASF or not — no Apache-Software-Foundation-specific assumptions baked in.

Maintainer-facing PR-queue management for projects with a public contributor PR queue. Nine skills that compose into a complete triage + review + mentoring + hygiene pass:

1. Agentic Triage — sweep open PRs, classify against the project's quality criteria, propose a disposition (draft / comment / close / rebase / rerun / mark ready / ping), execute on maintainer confirmation.
2. Stats — read-only summary tables of the open PR backlog, grouped by area label, so the maintainer can see where queue pressure is sitting before / after a triage sweep.
3. Code review — deep, line-aware code review one PR at a time. Reads the diff, applies the project's review criteria, drafts an APPROVE / REQUEST_CHANGES / COMMENT review with inline comments, posts on confirmation.
4. Quick-merge — express-lane screener for trivial, low-risk PRs (docs, changelog, translations, tests) that pass every quality gate; surfaces ranked candidates with diff summaries and the exact merge command for the maintainer to run. Never merges itself — automated merge is the framework's deliberately-deferred Agentic Autonomous mode.
5. Mentor — joins a PR (or issue) thread in a teaching register: clarifying questions, pointers to project conventions and docs, an explanation of why a change is being asked for. Waits for explicit maintainer confirmation before posting; never gatekeeps. Lives in the Mentoring mode but operates on the same PR surface as skills 1–4.
6. Stale-sweep — identify open PRs past a configurable inactivity threshold, classify as NUDGE or CLOSE-STALE, post one comment per PR on maintainer confirmation.
7. Pre-first-PR check — pre-flight a contributor's first PR against project conventions before it reaches a human reviewer; surfaces formatting, test, and documentation gaps.
8. Reviewer routing — suggest the best-fit reviewer(s) for a new PR based on path ownership, recent review history, and current load.
9. Stack review — review a GitHub stacked pull request as one unit: chain currency, file-by-layer matrix, removed-definition seams, narrative drift, and code read by tier with a coverage table. Drafts one rolling COMMENT on the lowest open layer and names the layers that deserve a code-review pass. Never approves.

Why a framework skill family? These skills were originally maintained inside one ASF project's developer-tooling repo as breeze pr auto-triage and breeze pr stats — useful for any ASF project with a meaningful contributor-PR queue, but locked behind that project's local toolchain. Lifting them into the framework lets other adopters reuse the playbook with their own adopter-config files for project-specific knobs (committers team handle, area-label prefix, comment-template wording, CI-check → doc-URL map, review-criteria source files).

Install just this family — one plugin, 9 skills. Maintainer-facing PR-queue management.

Once you have added the marketplace:

/plugin install magpie-pr-management@apache-magpie

New to Magpie? The quick start walks the whole path in one place — install, the first /magpie-setup run, and a recording of it happening — plus the other agents and the secure-isolation setup to run next.

Illustrative — the real run derives more and asks better. What is true is the shape: it runs itself, it writes only your personal layer, and it stages nothing.

Every skill here resolves project-specific values from the adopter's <project-config>/ directory — which is your personal layer first — .apache-magpie-local/ (gitignored) in a project that adopted Magpie, <git-common-dir>/apache-magpie/ in one that did not — then .apache-magpie-overrides/ (committed, the project's).

For yourself: /magpie-setup config scaffolds and fills these locally. Nothing is staged, nothing is committed, and it works on a repository that has never adopted Magpie.

For the project: /magpie-setup adopt commits them for every contributor, either scaffolded directly or promoted from what you configured locally.

Required. Without these a skill would act on a guess, so it stops and says which file is missing.

Optional. Each has a documented fallback; absent, the skill still runs.

Third-party packages, none of them required: this family works with none of them installed, and Magpie neither bundles nor depends on any. They are named because they are what a maintainer goes looking for next, and because the answer differs by agent.

Code Review — Anthropic

Automated pull-request review through several specialised agents, scored by confidence.

With this family: pr-management-code-review walks a maintainer through reviewing one PR at a time and drafts the review they post. This is the other half — a broad automated pass whose findings that review can weigh.

Available on Claude Code only.

Install commands per agent are in Companion skill packages.

Illustrative shapes, not real transcripts — your output will differ. Nothing below sends, merges, or posts anything without you confirming it.

Review a PR in depth.

> review PR #5193

  PR #5193  'Add retry to the S3 client'  +212 -18, 6 files
  2 blocking:   retry loop swallows KeyboardInterrupt (client.py:88)
                no test for the exhausted-retries path
  3 non-blocking nits. Review comment drafted, not posted.

Triage the whole queue.

/magpie-pr-management:pr-triage

See where the queue is stuck.

/magpie-pr-management:stats

• Top-level README — Install — 3-step bootstrap.
• projects/_template/README.md — adopter scaffold index, including the PR-management config files.
• tools/spec-loop/specs/pr-management-family.md — functional spec: acceptance criteria, validation commands, and known gaps.
• docs/mentoring/README.md — pr-management-mentor family overview.