api-enhancement-scanGiven a library or module name, survey every call site of it across the codebase — fanning out subagents over independent codebase sections — and surface recurring caller-side patterns (repeated boilerplate, copy-pasted wrappers, awkward argument plumbing, repeated post-processing) that a new or enh
canvasCheck, render and serve a typed canvas document as one reviewable page, and read the reviewer's comments and choices back from its answers sidecar. A document is a list of small block types (prose, question, figure, annotated-text, schema, operations, matrix, trace, precedence, plan, code-flow, work
capability-groomTake a capability from a name to a chosen shape and implementation architecture: define it, research prior art and constraints, propose two or three shapes, select one with stated criteria, and leave a capability entry and a decision ready to record. Use it before any task is split from a capability
decision-makeMake one decision in the open: state the question and its forcing drivers, research the facts and the prior art it rests on, write the options with consequences, choose with criteria written first, and record what would reopen it. Use it whenever a choice will constrain later work.
explainExplain one thing as a canvas document with no questions: the subject as typed blocks with numbered nodes anchored to the exact text, a walkthrough the reader comments on. Domains are notes beside this skill (sql today). Then hand it to canvas. Use it when the reader needs to understand something, n
explore-codebaseSystematic method for understanding an unfamiliar codebase: getting oriented in a new repo, locating where something is implemented, tracing how a feature or request flows end to end, and building an accurate mental model before answering questions or making changes. Use whenever you're dropped into
pr-statsSummarize a pull request or branch diff beyond GitHub's +/-: lines added and removed by code, comments, blank and prose; a change-category breakdown (added, deleted, renamed, tests, docs, generated, formatting-only, comment-only, logic); dependency and exported-API changes; and the cyclomatic-comple
propose-solutionPropose one solution as a canvas document that ends in a decision: the problem, the solution as typed blocks, and a question with a recommendation for every trade-off the reviewer must ratify, so the page can be approved or sent back. Domains are notes beside this skill (sql today). Then hand it to
researchAnswer one question with sourced findings inside a time box: state the question, search the repo before the web, record each source with what it settles, and end with findings, open points and a recommendation. Use it whenever a decision or a capability needs facts first.
skill-authorWrite or tighten a minimal skill: one process, a scope line, inputs and outputs, numbered steps, and optionally a map, extension points, grading checks and a test environment. Short, lists over prose, other skills called by wikilink. Script-free unless a step is deterministic and repeated. Use it fo
skill-reviewReview one skill or every skill in a plugin against the skill-author checks and against each other, and recommend what to tighten, map, merge, split, retire or document. Read-only; with --fix it hands each marked skill to skill-author.