microsoft/apm

APM Issue Autopilot drives any open microsoft/apm issue from raw intake to a mergeable PR with triage as the central gate. It batches issues, runs the triage panel per issue, presents one consolidated review, escalates by default, and only auto-implements clear, bounded accepts approved by the maintainer.

APM Review Panel runs a fan-out panel of specialist agents to review a labelled pull request in microsoft/apm. It aggregates findings from mandatory and conditional specialists plus a CEO synthesizer, then writes one advisory recommendation comment (no verdict labels, no merge gating). Use when a non-trivial PR needs cross-cutting recommendation on architecture, CLI logging, DevX UX, supply-chain

APM Spec Guardian runs a four-panel adversarial advisory review on pull requests that touch the OpenAPM specification, schemas, or conformance fixtures, returning a ship recommendation keyed off a shocked_meter scale. Use it when a PR changes normative spec artifacts and needs expert panel findings before a maintainer decides to ship.

APM Starter is a starter package for Agent Package Manager that demonstrates how to create reusable agent primitives like instructions, prompts, and agents. Use it to bootstrap new APM packages or learn the structure.

APM Strategy guides product positioning, release communication, community-facing artifacts, and breaking-change decisions. Activate it when editing README, manifests, changelogs, release workflows, or issue templates.

APM Triage Panel orchestrates multiple specialist personas to triage a single GitHub issue in the microsoft/apm repository, producing a synthesized comment with a triage decision, label set, milestone, and suggested next action.

Auth centralizes token management and credential resolution for the APM CLI, including GitHub and Azure DevOps PATs and az CLI bearer fallback. Activate when code touches authentication, tokens, git remote access, or credential errors.

Batch Bug Shepherd automates batch triage of suspected bugs: it fans out subagents, gates bugs against principles, detects existing PRs, opens TDD fixes, and drives PRs to mergeable via review and CI. Use it to triage issues, sweep a bug queue, or drive in-flight community PRs.

CLI Logging UX guides editing and creating CLI output, logging, warnings, error messages, progress indicators, and diagnostic summaries in the APM codebase. Use it when code touches console helpers, DiagnosticCollector, STATUS_SYMBOLS, CommandLogger, or any user-facing terminal output.

Cut Release assesses merged changes since the last tag, picks a patch or minor semver bump, sanitizes the unreleased changelog into a dated version block, bumps pyproject.toml and uv.lock, verifies lint, and opens a release PR.

Developer Tooling UX guides the design of APM CLI command surfaces, help text, install/init/run flows, error wording, and first-run experience. Activate when modifying Click command definitions, help strings, error messages, or README quickstart paths.

Docs Corpus Audit runs a whole-corpus regrounding pass over the documentation against current source code, page by page, and emits surgical fixes for stale claims. Use it when maintainers want a full docs audit, not per-PR drift review.

Docs Grounding Verifier verifies claim-level grounding of documentation pages against source code, returning per-claim verdicts with file:line evidence citations. Use it when you need to fact-check specific pages for accuracy, not for whole-corpus audits or PR triage.

Docs Impact Architect proposes structural documentation TOC deltas (new, moved, retired pages) and new-page outlines when a PR changes docs structure, ensuring the 3-promise narrative and persona ramps hold.

Docs Impact Classifier classifies the documentation impact of a pull request diff into no change, in-place edit, or structural change. It uses deterministic path gates, symbol extraction, and a bounded LLM call to keep docs-sync costs low when no docs work is needed.

Docs Impact Localizer translates a classifier's in-place verdict into a page-by-page documentation edit plan. It reads candidate pages, narrows changes to specific sections, flags cross-page consistency requirements, and returns JSON task briefs for doc-sync writers.

Docs Sync assesses whether documentation must change when a pull request opens, reopens, or synchronizes, detecting silent drift between code and docs. It classifies impact as no-change, in-place edit, or structural change, then orchestrates a panel to produce a patch-ready advisory without merging or pushing.

OSS Growth improves open source project adoption by refining README conversion surfaces, quickstarts, templates, release announcements, and contributor funnels. Use it when working on OSS adoption and growth tactics.

PR Description drafts a self-sufficient GitHub-Flavored Markdown pull request body with TL;DR, problem, approach, implementation, validated mermaid diagrams, trade-offs, validation evidence, and how-to-test sections. Use it when asked to write a PR description, draft a PR body, open a PR, or fill in a PR template.

Python Architecture guides the creation of new modules, refactoring class hierarchies, introducing design patterns, and making multi-file changes in the APM CLI codebase. Use it to follow existing patterns and centralize shared logic with regression tests and static checks.

Shepherd Driver drives one existing pull request to a mergeable state: classifies review, runs the review panel, folds recommendations, pushes, watches CI, and resolves conflicts under caps. Use it as the composed per-PR stage in a batch bug shepherd or issue autopilot orchestrator, not standalone.