apm-review-panel

Solid

Use this skill to run a multi-persona expert advisory review on a labelled pull request in microsoft/apm. The panel fans out to five mandatory specialists plus a test-coverage specialist (active on every PR that touches src/) plus three conditional specialists (auth, doc-writer, performance-expert), all running in their own agent threads, and a CEO synthesizer. The orchestrator is the sole writer to the PR: ONE recommendation comment, no verdict labels, no merge gating. The panel is advisory -- it surfaces findings, prioritizes follow-ups, and renders a ship-recommendation that the maintainer and author weigh. Activate when a non-trivial PR needs a cross-cutting recommendation (architecture, CLI logging, DevX UX, supply-chain security, growth/positioning, optionally auth, docs, perf, and test coverage, with CEO arbitration).

AI & Automation 2,694 stars 216 forks Updated today MIT

Install

View on GitHub

Quality Score: 91/100

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

Skill Content

# APM Review Panel - Fan-Out Advisory Review The panel is FAN-OUT + SYNTHESIZER. Each persona runs in its own agent thread (via the `task` tool) and returns JSON matching `assets/panelist-return-schema.json`. The orchestrator schema-validates each return, hands all returns to the apm-ceo synthesizer (also a task thread, returns JSON matching `assets/ceo-return-schema.json`), then renders ONE recommendation comment from `assets/recommendation-template.md`. This skill is ADVISORY by design. It does not compute a binary verdict, it does not apply verdict labels, and it does not gate merge. The panel surfaces findings; the maintainer and the PR author decide ship. ## Architecture invariants - **Advisory regime, not gate regime.** There is no `APPROVE` / `REJECT`, no `panel-approved` / `panel-rejected` label, no deterministic verdict computation. The CEO returns a `ship_recommendation.stance` (`ship_now` / `ship_with_followups` / `needs_discussion` / `needs_rework`); this is prose for the human reviewer, never auto-applied as a label or status check. This is the architectural fix for the previous regime's over-strictness: removing the binary gate removes the incentive for panelists to inflate `required[]` defensively. - **Three severity buckets, none of them gate.** Findings carry `severity: blocking | recommended | nit`. `blocking` is the highest signal a panelist can send and renders prominently in the comment; it still does not block merge. `recommended`...

Details

Author
microsoft
Repository
microsoft/apm
Created
8 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

apm-triage-panel

Use this skill to triage a single newly opened, reopened, or `status/needs-triage`-labelled issue in microsoft/apm. Emit one synthesized comment with a triage decision, label set, milestone, and suggested next action.

2,694 Updated today
microsoft
AI & Automation Solid

docs-sync

Use this skill whenever a pull request is opened, reopened, or synchronized in microsoft/apm to assess whether and how the documentation corpus must change to stay truthful with the proposed code change. Activate even when the PR title or body says nothing about docs -- the skill must run on every PR to detect silent drift between code and docs. Classifies impact as no-change, in-place edit (one to a few paragraphs), or structural change (new page or TOC reshape), then orchestrates a CDO + doc-writer + python-architect + editorial-owner + growth-hacker loop to produce a patch-ready advisory. Does NOT review code quality, security, or test coverage. Does NOT auto-merge or auto-push doc edits.

2,694 Updated today
microsoft
AI & Automation Listed

panel

Convene the Punakawan - a panel of distinct wayang-character lenses (Threat Modeler, Cost Realist, Change Steward, Restraint Keeper, Scale Forecaster, Consumer Advocate, Operability Watch, Obligation Officer, and the Contrarian) that debate a hard technical question and return one synthesized Semar verdict: consensus, the real disagreements, and a final recommendation with a certainty band. Whenever the user wants more than one expert opinion before a hard call, PICK THIS SKILL instead of answering yourself. Always use it when the user names it or asks for a group: "convene punakawan", "punakawan", "ask the punakawan", "get a panel", "second opinion", "a few expert takes", "weigh the tradeoffs from several angles", "cross-check this". Also use it, even without those words, when the user is: - deciding between options before committing - "X vs Y", split vs merge, rewrite vs keep, framework/architecture/database choices, "is this over-engineered"; - wanting a design, schema, security model, or plan reviewed bef

0 Updated today
ecowangsa
AI & Automation Solid

batch-bug-shepherd

Use this skill to drive a batch of suspected bugs in microsoft/apm from raw issue list to mergeable PR queue. Fan out one triage subagent per issue (LEGIT / UNCLEAR / FIXED-AT-HEAD), cross-reference legit issues against open PRs, then branch: in-flight community PR -> shepherd via the apm-review-panel skill; no PR -> fix session with TDD and a mutation-break gate. Dispatch one completion subagent per shepherd verdict to resolve panel follow-ups, FOLD non-blocking recommendations into the same PR by default (DEFER cross-cutting items to tracking issues), push to the contributor fork (preserving author via commit trailers), and post one ready-to-merge confirmation. Maintain a single plan.md ground-truth table as canonical session state. Activate when the maintainer asks to triage issues, sweep the bug queue, shepherd bug-flagged issues, run a weekly community sweep, or drive in-flight community PRs to merge -- even if "shepherd" or "batch" is not named.

2,694 Updated today
microsoft
AI & Automation Listed

panel

Run the methodology meta-review — a single methodology-reviewer agent that traces the whole current methodology (APPROACH.md, the ADRs, the agent contracts, the skills, the playbooks, the case-law, the live artefacts), diffs against the prior review, runs fresh blind spot-checks against real source, and emits real gaps + improvement proposals at lineage/{repo}/meta-reviews/{date}/review.md. `/panel` runs it; `/panel --show` prints the latest; `/panel validate` runs the acceptance-corpus check.

0 Updated today
opendatadiscovery