pr-management-quick-merge
starsforks
How to install pr-management-quick-merge?
apache/magpie/pr-management-quick-merge
$npx -y skills add apache/magpie --skill pr-management-quick-mergeIdentify trivial, low-risk pull requests in the ready for maintainer review queue of <upstream> that pass every quality gate and touch only supplementary areas (docs, changelog, translations, tests) — the "express lane" a maintainer can review and merge in seconds. Surfaces and
SKILL.md
| 1 | <!-- SPDX-License-Identifier: Apache-2.0 |
| 2 | https://www.apache.org/licenses/LICENSE-2.0 --> |
| 3 | |
| 4 | <!-- Placeholder convention: |
| 5 | <repo> → target GitHub repository in `owner/name` form (default: read from `<project-config>/project.md → upstream_repo`) |
| 6 | <viewer> → the authenticated GitHub login of the maintainer running the skill |
| 7 | <base> → the PR's base branch (typically `main`) |
| 8 | <project-config> → the adopter's config directory (`.apache-magpie-overrides/` in an adopter repo) |
| 9 | Substitute these before running any `gh` command below. --> |
| 10 | |
| 11 | # pr-management-quick-merge |
| 12 | |
| 13 | This skill answers one question for the `ready for maintainer review` queue: |
| 14 | |
| 15 | > *Which of these PRs are so small and so low-risk that the maintainer can |
| 16 | > read the whole diff, confirm it, and merge it in under a minute — and which |
| 17 | > are already passing every quality gate so that nothing stands between |
| 18 | > "looks good" and "merged"?* |
| 19 | |
| 20 | It is the **express lane** of the PR lifecycle. `pr-management-triage` decides |
| 21 | *whether to engage* with a PR and promotes the survivors to |
| 22 | `ready for maintainer review`. `pr-management-code-review` does the deep, |
| 23 | line-level read of the substantive ones. This skill skims off the trivial tail |
| 24 | — typo fixes, doc clarifications, changelog/newsfragment entries, translation |
| 25 | strings, small test-only changes — so the maintainer can clear them in a |
| 26 | single fast pass instead of letting them age in the queue behind the |
| 27 | heavyweight PRs. |
| 28 | |
| 29 | The skill **never merges**. It surfaces and ranks candidates and hands the |
| 30 | maintainer everything needed to act — the full file list, the churn, an |
| 31 | explicit all-gates-green attestation, a `[V]iew diff`, and the exact |
| 32 | `gh pr merge` command the maintainer runs in their own session. Its **only** |
| 33 | state-changing action is an optional **APPROVE review**, submitted solely on |
| 34 | the maintainer's explicit per-PR confirmation — the same |
| 35 | assistant-drafts/maintainer-fires pattern |
| 36 | [`pr-management-code-review`](../pr-management-code-review/SKILL.md) already |
| 37 | uses. That exists so the maintainer can clear the common case where a trivial, |
| 38 | all-green PR simply has no approval yet and branch protection needs one. It |
| 39 | does **not** merge, label, comment, or convert. See |
| 40 | [Golden rule 1](#golden-rules), [the approve action](#step-3b--optional-approve-action), |
| 41 | and [Why the skill does not merge](#why-the-skill-does-not-merge-agentic-autonomous). |
| 42 | |
| 43 | Detail files in this directory: |
| 44 | |
| 45 | | File | Purpose | |
| 46 | |---|---| |
| 47 | | [`candidate-rules.md`](candidate-rules.md) | The two-stage screen — quality-gate gate (hard pass/fail) then triviality classification (footprint + path allow/deny + tier). The only file needed at decision time. | |
| 48 | | [`<project-config>/pr-management-quick-merge-config.md`](../../projects/_template/pr-management-quick-merge-config.md) | Per-project thresholds, allow/deny path globs, merge-command template. | |
| 49 | |
| 50 | This skill reuses the `pr-management` family's shared machinery rather than |
| 51 | re-implementing it: |
| 52 | |
| 53 | - **Pre-flight** — [`pr-management-triage/prerequisites.md`](../pr-management-triage/prerequisites.md). |
| 54 | - **Batched fetch + session cache** — [`pr-management-triage/fetch-and-batch.md`](../pr-management-triage/fetch-and-batch.md), extended with a `files` connection (see [Step 1](#step-1--fetch-the-ready-queue)). |
| 55 | - **Real-CI guard** — [`pr-management-triage/classify-and-act.md#real-ci-guard`](../pr- |
People who liked this also viewed
6 picksType
- requesting-code-reviewUse when completing tasks, implementing major features, or before merging to verify work meets requirementsSkillsJul 2026
- code-reviewSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- receiving-code-reviewUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performativeSkillsJul 2026
- baoyu-format-markdownFormats plain text or markdown files with frontmatter, titles, summaries, headings, bold, lists, and code blocks. Use when user asks to "format markdown", "beautify article", "add formatting", or imprSkillsJul 2026
- code-review-excellenceMaster effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing reSkillsJul 2026
- code-review-and-qualityConducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensiSkillsJul 2026
