Skip to content
v4.0.0MIT

Software-engineering workflow skills: diagnose bugs from tickets, specs, or a description down to their root cause, turn a design conversation into a spec file, plan how to build a spec, tickets, or an agreed design against the real code, step by step with the test each step writes first, implement it with the session's model orchestrating worker subagents on a cheaper model, review code for correctness, the repo's written standards, and conformance to a spec, then commit with staging and message conventions and write the PR title and description.

diagnose

Investigate one or more bugs down to their root cause, without fixing them. A bug can come from GitHub issues, Azure DevOps work items, a spec whose code misbehaves, a bug-report file, a free-text description, or the conversation, and related items can go in one run. Reproduces where it can, labels each root cause confirmed, likely, or hypothesis, groups the items by cause, and hands off to /swe:plan through an Agreed fix block, or adds the fix's criteria to the target spec. Usage: /swe:diagnose [target …] [context]. User-invoked only.

Compatibility
Needs git for history, bisect, and temporary instrumentation; outside a repository it reads code only. Ticket targets are read by the skill swe:fetch-tickets, called by name, else pasted by the user. Hosts that ignore disable-model-invocation lose the user-only invocation guarantee.
Read SKILL.md at the source

Pinned to revision e88ad6d185e8, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.