magpie-pr-management-quick-merge

<!-- SPDX-License-Identifier: Apache-2.0 https://www.apache.org/licenses/LICENSE-2.0 --> <!-- Placeholder convention: <repo> → target GitHub repository in `owner/name` form (default: read from `<project-config>/project.md → upstream_repo`) <viewer> → the authenticated GitHub login of the maintainer running the skill <base> → the PR's base branch (typically `main`) <project-config> → the adopter's config directory (`.apache-magpie-overrides/` in an adopter repo) Substitute these before running any `gh` command below. --> # pr-management-quick-merge This skill answers one question for the `ready for maintainer review` queue: > *Which of these PRs are so small and so low-risk that the maintainer can > read the whole diff, confirm it, and merge it in under a minute — and which > are already passing every quality gate so that nothing stands between > "looks good" and "merged"?* It is the **express lane** of the PR lifecycle. `pr-management-triage` decides *whether to engage* with a PR and promotes the survivors to `ready for maintainer review`. `pr-management-code-review` does the deep, line-level read of the substantive ones. This skill skims off the trivial tail — typo fixes, doc clarifications, changelog/newsfragment entries, translation strings, small test-only changes — so the maintainer can clear them in a single fast pass instead of letting them age in the queue behind the heavyweight PRs. The skill **never merges**. It surfaces and r...