Loading...
Loading...
Found 167 Skills
Verify whether a GitHub issue is fixed in the local codebase. User provides a GitHub issue URL, the skill fetches it, extracts reproduction steps, builds the product from source, runs the reproduction steps, and reports whether the issue still exists or not.
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.
Use when implementing a GitHub issue end-to-end — MANDATORY for all dev tasks; spawns a repo worker devbox through speckit phases.
Create a GitHub issue with title and description. Use when the user wants to file a bug, request a feature, or create a tracking issue.
Fix GitHub issues end-to-end — from analysis through branch creation, implementation, testing, and PR submission. Use this skill whenever the user mentions fixing a GitHub issue, resolving a bug from an issue tracker, working on a GitHub issue number, or says things like "fix issue
Use when an issue needs deeper analysis than triage — confirming root cause by reading code, verifying file/line references in body are still valid, checking blast radius across the codebase, or proposing a concrete fix direction. One issue per invocation.
Analyze a GitHub issue and create a detailed technical specification
Use when given a GitHub issue URL or number to investigate and implement a fix. Triggers on "fix issue", "fix bug", "fix
Use when converting a new GitHub issue into a structured PRD, or posting clarifying questions when the issue is underspecified.
Load all open issues from GitHub and save them as markdown files
Create a plan collaboratively with the user, then convert the approved plan into a GitHub issue.