apme

Guide for handling pull request reviews, including automated (Copilot, CodeRabbit) and human reviewer feedback. Use when responding to PR comments, resolving review threads, or updating PRs after review.

Prepare and submit a pull request for the APME project. Syncs with upstream, creates a feature branch, runs quality gates (tox -e lint, tox -e unit), updates documentation and ADRs as needed, commits with conventional commits, then creates the PR via gh. Use when the user asks to submit, create, or open a pull request, or says "submit PR", "open PR", "create PR", "new PR".

Create an Architecture Decision Record. Use when documenting an architecture decision, "record this choice", "we decided to use X", or after resolving an architectural DR. Do NOT use for capturing questions (use dr-new instead) or reviewing existing ADRs (use sdlc-status instead).

Compare the agentskills.io specification against this project's extended frontmatter allowlist to determine whether the custom validation hook (scripts/check_skill_frontmatter.py) is still needed. Use when checking if the upstream spec has adopted the extended fields, when planning to remove the custom hook, or when a new spec release is announced.

Audit documentation coverage against common user questions. Generates a Q&A matrix, searches docs/code for answers, flags gaps, and creates DRs for missing content. Use when asked to "audit docs", "check documentation coverage", "what questions can users answer", or before releases/demos.

Review and help prepare a contributor's pull request (upstream or fork). Use when the user asks to review a PR, get a contributor PR ready, update a contributor's branch, or ensure a PR meets project standards before merge. Follow this skill so contributor PRs are reviewed consistently and avoid rework (lint/test failures, outdated base, weak description).

Align branch name with artifact ID when they mismatch. Use when: renumbering a REQ/DR/ADR after branch creation, "branch name is wrong", "rename branch to match", or when PR review flags branch/artifact mismatch. Handles the git branch rename and remote update.

Reference for running lint, test, build, and pod commands via tox. Agents MUST use tox for all quality gates — never invoke pytest, ruff, mypy, prek, or shell scripts directly. This skill is the canonical lookup table for which tox environment to use.

Guide for writing and modifying GitHub Actions workflows in this repository. Use when creating CI/CD pipelines, adding workflow jobs, modifying build steps, or debugging CI failures. Enforces the project's lean CI philosophy.

Create implementation tasks for a requirement. Use when breaking down a REQ, "add task to REQ-001", "create work items", or after approving a requirement. Do NOT use for creating requirements (use req-new instead) or reviewing task status (use sdlc-status instead).

Capture an external RFE (Jira, customer request, feature idea) using a research-first approach. Use when: "capture this Jira", "customer RFE", "feature request from X", "AAPRFE-123 should be tracked". This skill researches existing capabilities BEFORE creating specs to avoid duplicating what already exists. Do NOT use for internal feature ideas already discussed (use req-new instead).

Scan project dependencies and CI workflows for known vulnerable packages. Use when checking for security issues, "scan for vulnerabilities", "check for compromised packages", or after a security advisory is published. Extensible via references/vulnerable-packages.md.

Resolve open Decision Requests. Use when deciding DRs, resolving blockers, "what should we do about DR-X", "decide the blocking question", or when `/sdlc-status` shows blocking DRs. Do NOT use for creating new DRs (use dr-new instead) or just viewing status (use sdlc-status instead).

Create a Requirement spec. Use when adding a new feature, "I want to spec out X", "new feature request", "create REQ for this", or when ready to formalize a feature idea. Do NOT use for creating tasks (use task-new instead) or bulk importing from PRD (use prd-import instead).

Create a Decision Request. Use when you have a question that needs deciding, "we need to make a decision about X", "capture this as a DR", "log this blocking question", or after discussing something that needs formal resolution. Do NOT use for resolving DRs (use dr-review instead) or documenting decided architecture (use adr-new instead).

Create a delivery phase for grouping requirements. Use when defining roadmap phases, "add a phase", "create Phase 2", or organizing requirements into delivery milestones. Do NOT use for importing phases from a PRD (use prd-import instead) or creating requirements (use req-new instead).

Import a Product Requirements Document and create SDLC artifacts. Use when you have a PRD to break down, "import this PRD", "create specs from requirements doc", or starting a new project from a PRD. Do NOT use for updating existing artifacts or creating individual requirements (use req-new instead).

Show project status, progress, and blockers. Use when asking "what's the status?", "where are we?", "what's blocking?", "show me progress", or starting a work session. Do NOT use for creating or modifying artifacts (use req-new, dr-new, etc. instead).

Get workflow guidance for spec-driven development. Use when unsure what to do next, "help me get started", "what should I work on", "I'm stuck", or starting a new session. Do NOT use for directly creating artifacts (this skill guides you to the right skill for that).