A read-only report that finds simple, low-risk pull requests in the ready-for-review queue and ranks them. It focuses on changes to supplementary areas such as documentation, changelogs, translations, and tests.

Use it to identify likely quick merges and inspect each candidate's change summary and quality checks.

It helps maintainers find changes that may be quick to review instead of searching the whole review queue manually.

quick-merge — Skill for Claude Code by apache/magpie

About the project

Apache Magpie is a framework of agent-assisted workflows for maintaining Apache software projects, including issue triage, pull-request review, contributor mentoring, and security-report handling. Apache maintainers and developers use it to delegate repetitive project work to coding agents while retaining human review. Its catalogue entries are the skills, instructions, plugin, and settings that implement these workflows.

apache/magpie · 118 stars · on GitHub · magpie.apache.org

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add apache/magpie --skill quick-merge

Clone the repo

git clone --depth 1 https://github.com/apache/magpie

Made for: Claude Code.

Or install magpie-pr-management, the plugin that ships this one along with the rest of its 9 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/apache/magpie/quick-merge/github.svg)](https://agentmods.dev/skills/apache/magpie/quick-merge)

Your own site

<a href="https://agentmods.dev/skills/apache/magpie/quick-merge"><img src="https://agentmods.dev/badge/skills/apache/magpie/quick-merge/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/apache/magpie/quick-merge"><img src="https://agentmods.dev/badge/skills/apache/magpie/quick-merge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 123 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,159 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00123	$0.03159
Opus 5.5	$0.00049	$0.01264
Sonnet 5.5	$0.00025	$0.00632
Haiku 4.5	$0.00012	$0.00316

Measured today against content hash 8952f9dec339, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

quick-merge scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/magpie-pr-management/skills/quick-merge/SKILL.md · 246 lines

How it starts

The opening of the file, as written. The whole thing — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.

pr-management-quick-merge

Pre-flight — is this project set up?

Do this first, before anything else in this skill, and do it silently. One command answers it and carries its own rules; there is nothing else to read.

Run the checker with this skill's own frontmatter name: and surface_hash:, and one --requires for each requires_config: entry:

PYTHONPATH=".apache-magpie-local:$(git rev-parse --git-common-dir)/../.apache-magpie-local:$(git rev-parse --git-common-dir)/apache-magpie" \
  python3 -m setup_preflight --skill <name> --hash <surface_hash> [--requires <file>]...

The path finds the checker /magpie-setup:setup config installed in the personal layer: this checkout's .apache-magpie-local/, the main checkout's when this is a linked worktree, or the git directory's apache-magpie/ when Magpie is only installed.

{"verdict": "ok"} → silent. Continue into the work the user asked for and say nothing about pre-flight. This is the ordinary answer.
{"verdict": "action", ...} → each finding names a section, and rules carries that section's text. Follow it. The facts are the inputs; what to propose, and what may not be done, are in the rules rather than here. Act on a finding only through its rules.
The command did not run at all — no such module, a non-zero exit, no python3 — → never read that as a pass, and do not re-derive the check by hand: it lives in code so that there is one version of it. If the project has no .apache-magpie.lock, .apache-magpie-overrides/, or personal layer (any of the three directories above), nothing has been set up here and there is nothing to reconcile — resolve this skill's requires_config: entries yourself (first match wins: .apache-magpie-local/<file>, the main checkout's .apache-magpie-local/<file>, <git-common-dir>/apache-magpie/<file>, then .apache-magpie-overrides/<file>), stay silent if they all resolve, and run /magpie-setup:setup config for this skill if any does not, which also installs the checker. Otherwise the project is set up and its checker is missing or stale: say so, propose /magpie-setup:setup config to install it or /magpie-setup:setup upgrade to refresh it, and carry on with the work.

Read the full file on GitHub · 246 lines

Files

What ships with it

22 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

today Changed · +2 lines 8952f9dec339
5d ago Changed · -109 lines a22ea5b4638c
6d ago Changed ed75c9533090
10d ago Changed · +7 lines 9689e3a2764c
16d ago Changed 01c6713da4bf
19d ago Changed · -204 lines · -59 tokens per session adf42a084684
22d ago Changed · -5 tokens per session e42fb82d385f
23d ago Changed · -94 lines 80104ff2c471
27d ago Changed · +33 lines b43b04f75a9f
1mo ago First seen · 611 lines · 187 tokens per session scan A 736fdad34328

Subscribe to this mod's changes

quick-merge is a skill published in the GitHub repository apache/magpie (118 stars, last pushed today), licensed Apache-2.0. It adds 123 tokens to every session and 3,159 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-14.

CVE Claude Code Code review Project management Security agent-skills apache automation

tech-debt

Track, categorize and prioritize technical debt across the codebase — scans for debt indicators, maintains a register.

Donchitos/Claude-Code-Game-Studios · 25 tokens

issue-creation

Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.

Gentleman-Programming/gentle-ai · 30 tokens

maintain

Triage and work through Ouroboros GitHub issues and pull requests as a maintainer. Use for ooo maintain, backlog cleanup, review, merge readiness, duplicate PRs, and issue disposition.

Q00/ouroboros · 44 tokens

systemic-issue-triage

Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.

Gentleman-Programming/gentle-ai · 57 tokens

spec-kitty-runtime-review

Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only…

Priivacy-ai/spec-kitty · 85 tokens

ring:planning-large-features

Planning the 8-gate Large Track pre-dev workflow (research, PRD, feature map, TRD, API contract, data model, dependency map, plan) with per-gate human approval. Use for features 2+ days that add dependencies, data models, multi-service integration, or new architecture. Skip for small features (use…

LerianStudio/ring · 89 tokens