apm-issue-autopilot

Drives GitHub issues from triage through implementation to mergeable pull requests.

3.7k|344|Updated Sep 18, 2025
One-click install
npx skills add https://github.com/microsoft/apm --skill apm-issue-autopilot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apm-issue-autopilot
Source: https://github.com/microsoft/apm/tree/main/.agents/skills/apm-issue-autopilot
Command: npx skills add https://github.com/microsoft/apm --skill apm-issue-autopilot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

Clearing an open issue backlog by hand means triaging each issue, deciding what is safe to automate, writing the fix, opening a PR, and chasing CI and review feedback until mergeable. This Skill orchestrates that entire intake-to-merge pipeline for a batch of microsoft/apm issues while keeping a human maintainer in control at a single consolidated review checkpoint.

Core Features & Use Cases

  • Batch triage with escalate-by-default gating: Runs a triage rubric per issue in parallel, then presents one consolidated digest; only clear, bounded, high-confidence accepts proceed, and anything doubtful escalates to the maintainer.
  • Worktree-isolated solution pipelines: Each approved issue gets its own git worktree and an Ideate-to-Plan-to-Implement pipeline with typed coverage gates (regression traps for bugs, acceptance tests for features, docs builds for docs).
  • Drive-to-merge shepherding: Accepted PRs are driven to mergeability with CI watching, review follow-up folding, and conflict resolution, with caps on iterations and no auto-merge.
  • Use Case: A maintainer says "run the open backlog to mergeable PRs"; the Skill triages every issue, presents one review, implements the approved ones in isolated worktrees, and returns a final report of ready-to-merge PRs and escalated items.

Quick Start

Ask the agent to run the open microsoft/apm issue backlog through triage and drive the approved issues to mergeable pull requests.

Frequently Asked Questions about apm-issue-autopilot

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically turn a GitHub issue backlog into pull requests?

Invoke this skill manually with an issue list, search query, or the open backlog. It triages each issue in parallel, presents one consolidated review for your approval, then implements approved issues in isolated git worktrees and opens one PR per issue.

How does the triage confidence gate decide what gets auto-implemented?

Only issues triaged as accept with high confidence, no red flags, a supported type, and a complete implementation brief are marked auto-proceed. Anything doubtful, such as breaking changes, auth or security surfaces, or unbounded scope, escalates to the maintainer by default.

Can this skill merge pull requests automatically?

No. The skill never auto-merges and never auto-closes escalated issues. It drives each PR to a mergeable state with green CI and resolved conflicts, but the human maintainer approves the protected merge.

What happens when an issue is too risky or unclear to automate?

The confidence gate routes it to the maintainer in the single Phase 2 review with its red flags and reasoning. Escalated issues are surfaced in the final report for human action and are never auto-closed or auto-declined.

Does this skill work for a single issue or single PR review?

No, it is designed for batch intake-to-merge work over a queue. Single-issue triage belongs to apm-triage-panel, single-PR review to apm-review-panel, and bugs-only queue sweeps to batch-bug-shepherd, all of which are sibling skills.