magpie-pr-management-code-review

Solid

Walk a maintainer through deep, sequential code review of open pull requests on the configured `<upstream>` repo. Defaults to the **"my reviews"** queue (the union of five maintainer signals — see the Inputs table); selectors can narrow to a single PR, an area label, or a collaborator subset. Drafts an `approve` / `request-changes` / `comment` review per PR and posts on the maintainer's confirmation.

Code & Development 83 stars 78 forks Updated yesterday Apache-2.0

Install

View on GitHub

Quality Score: 84/100

Stars 20%
64
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

<!-- 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`) Substitute these before running any `gh` command below. --> # pr-management-code-review This skill walks a maintainer through **deep, line-aware review** of open pull requests, **one PR at a time**. Its job is to answer two questions per PR: > *Does this code meet the project's quality bar?* > *If not, what specifically should change before it lands?* It is the review-bench counterpart to [`pr-management-triage`](../pr-management-triage/SKILL.md). Triage decides whether to *engage* with a PR (draft / comment / close / rebase / rerun / mark-ready / ping). This skill takes PRs that have already cleared triage (or any other curated selector) and produces an actual code review — flagged findings, suggested changes, and a final `APPROVE` / `REQUEST_CHANGES` / `COMMENT` submission posted via `gh pr review`. Detail files in this directory break the logic out topic-by-topic: | File | Purpose | |---|---| | [`prerequisites.md`](prerequisites.md) | Pre-flight — `gh` auth, repo access, plugin / adversarial-reviewer detection. | | [`selectors.md`](selectors.md) | Input parsing — default `revie...

Details

Author
apache
Repository
apache/magpie
Created
3 months ago
Last Updated
yesterday
Language
Python
License
Apache-2.0

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

magpie-pr-management-triage

Sweep open pull requests on the configured `<upstream>` repo, classify each one against the project's quality criteria, propose a disposition, and — on the maintainer's confirmation — carry out the action via `gh`. Disposition options per PR: draft / comment / close / rebase / CI-rerun / workflow-approve / ping-stale-reviewer / request author confirmation of readiness / mark `ready for maintainer review` / promote bot-authored draft. Does **not** perform code review — that lives in `pr-management-code-review`.

83 Updated yesterday
apache
Code & Development Solid

magpie-pr-management-quick-merge

Identify 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 ranks candidates with per-PR diff summaries, an all-gates-green attestation, and the exact merge command. On the maintainer's explicit per-PR confirmation it can submit an APPROVE review (the maintainer's own review of the trivial diff — useful when the PR has no approvals yet and branch protection needs one), exactly as pr-management-code-review does. It never merges itself — automated merge is the framework's deliberately-deferred Agentic Autonomous mode; the maintainer runs the printed merge command in their own session.

83 Updated yesterday
apache
Code & Development Listed

review

Review, audit, sanity-check, look-at any review-able target. Triggers on a GitHub PR URL (fetched via the gh CLI), a local path or "." (review the working tree), a markdown/doc file, or a comment-thread URL. Read-only by default; --fix applies accepted findings locally and pushes to the PR branch after confirmation (never force, never merge, never to a protected branch). Produces severity-tiered findings (blocker / critical / should / may / nit) with path:line and <=15-word verbatim evidence quotes. Six dimensions: correctness, tests, security, performance, readability, consistency. For a deep PR review with cross-file code-context retrieval, use /adk:pr-review.

0 Updated 4 weeks ago
sujeet-pro