Engineering skill catalog
Every skill in the engineering plugin, grouped by what it's for. Each row links to a dedicated page with the full instructions, trigger phrases, and skills it pairs with. 34 skills total.
Stacked-PR workflow
The stacked-PR workflow: spec a feature, implement it as a chain of small PRs, address review comments, rebase the next PR on top, repeat.
-
/engineering:implementImplement an existing epic as a chain of stacked PRs, one per sub-issue, in order. Use when user wants to implement an epic, build out a planned feature, or execute on a `/spec`-produced plan. Pairs w…
-
/engineering:nextReset the working tree between tasks. Checks out a clean `dummy` branch rebased on latest `main` so the next task starts from a known good state. Use when user says "next", "start fresh", "reset for t…
-
/engineering:reviewAddress PR review comments interactively. Fetch comments, group by file, triage each one (fix or decline with reasoning), and post inline replies. Use when user says "address the PR comments", "go thr…
-
/engineering:specRefine a feature into a tracked epic with ordered sub-issues, each mapping to one PR. Use when user wants to spec a feature, plan a feature, break a feature into issues, or scope a new initiative. Doe…
-
/engineering:toprRebase a stacked PR onto the latest origin/main, correctly dropping commits already merged via squash-and-merge. Use when user wants to refresh a stacked PR after an earlier PR in the stack merged, or…
Code review & quality
Catch problems before they ship. Multiple review lenses (general, fresh-eyes, security, second-opinion) and a coverage-gap survey.
-
/engineering:careful-reviewRe-read the code you just wrote (and anything else you modified) with fresh eyes and look hard for bugs, errors, awkward design, dead code, or things that will confuse the next reader. Then fix what y…
-
/engineering:code-reviewReview code changes for security, performance, and correctness. Trigger with a PR URL or diff, "review this before I merge", "is this code safe?", or when checking a change for N+1 queries, injection …
-
/engineering:codex-reviewLowest severity to fix automatically — "p0", "p1" (default), or "p2".
-
/engineering:find-missing-testsSurvey a module, file, or PR for missing test coverage. Produce a specific, non-hallucinated list of test cases that should exist, with enough detail that another developer (or agent) can implement th…
-
/engineering:security-reviewSecurity-focused review of a code change or module. Covers OWASP top-10 risks (injection, auth bypass, IDOR, SSRF, secrets in code, unsafe deserialization) plus language-specific footguns. Produce a p…
Testing
Test-first development with real signal, plus end-to-end smoke testing of the deployed app.
-
/engineering:e2e-testRun a comprehensive end-to-end test of an app against real backend + frontend dev servers, with mocks disabled. Hits API endpoints directly, then drives the UI through a browser, and produces a PASS /…
-
/engineering:tddTest-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first develo…
-
/engineering:testing-strategyDesign test strategies and test plans. Trigger with "how should we test", "test strategy for", "write tests for", "test plan", "what tests do we need", or when the user needs help with testing approac…
Architecture & design
Architectural decisions and system design at the start of a feature. Different from refactoring an existing codebase.
-
/engineering:architectureCreate or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a syste…
-
/engineering:system-designDesign systems, services, and architectures. Trigger with "design a system for", "how should we architect", "system design for", "what's the right architecture for", or when the user needs help with A…
Engineering disciplines
Habits for hard problems: disciplined diagnosis, throwaway prototypes, getting grilled on a plan, zooming out, finding deepening opportunities in the codebase.
-
/engineering:diagnoseDisciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", report…
-
/engineering:grill-meInterview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their …
-
/engineering:grill-with-docsGrilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to…
-
/engineering:improve-codebase-architectureFind deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunitie…
-
/engineering:prototypeBuild a throwaway prototype to flesh out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI v…
-
/engineering:tech-debtIdentify, categorize, and prioritize technical debt. Trigger with "tech debt", "technical debt audit", "what should we refactor", "code health", or when the user asks about code quality, refactoring p…
-
/engineering:zoom-outTell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.
Planning & triage
Turn conversations into PRDs, PRDs into issues, and route issues through a triage state machine.
-
/engineering:to-issuesBreak a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementatio…
-
/engineering:to-prdTurn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
-
/engineering:triageTriage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manag…
Operations
The day-to-day mechanics: debug, deploy checklist, incident response, standups, docs.
-
/engineering:debugStructured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when be…
-
/engineering:deploy-checklistPre-deployment verification checklist. Use when about to ship a release, deploying a change with database migrations or feature flags, verifying CI status and approvals before going to production, or …
-
/engineering:documentationWrite and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of techn…
-
/engineering:incident-responseRun an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update mid-in…
-
/engineering:standupGenerate a standup update from recent activity. Use when preparing for daily standup, summarizing yesterday's commits and PRs and ticket moves, formatting work into yesterday/today/blockers, or struct…
Setup & tooling
One-time scaffolding for a repo: domain docs, pre-commit hooks, git guardrails, shipping flow.
-
/engineering:git-guardrails-claude-codeSet up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hoo…
-
/engineering:setup-engineering-skillsSets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain do…
-
/engineering:setup-pre-commitSet up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit…
-
/engineering:ship-prCommit all changes, push the current branch, and open a pull request against the default branch. Stages safely (skips .env / credentials / secrets), writes a commit message that matches the repo's sty…