Review a code change against its spec and the repo's own conventions, and report only findings you have proven: reproduced bugs, unmet requirements, code nothing needs, and broken house rules, ending in a PASS or FIX verdict.
Explain any topic simply for a newcomer — a concept, a system, a process, or part of a codebase — and save it as an HTML page with compiled architecture, workflow, sequence, data-flow, and lifecycle diagrams. Use when the user types /explain <topic>.
Use when writing or editing prose humans will read—blog posts, social media posts, documentation, READMEs, announcements, explanations, reports, commit messages, error messages, or UI text. Applies Steven Pinker's classic style and curse-of-knowledge remedies…
Group uncommitted changes into logical conventional commits, push them to a feature branch, and open a GitHub pull request with a release-please friendly description. Use when the user types /create-pr or asks to commit their changes and open a PR.
Use before writing, editing, fixing, refactoring, or reviewing ANY code, including small routine changes you could make without help: those are exactly where over-building slips in. Keeps the change minimal: YAGNI, reuse what the codebase already has, stdlib…
Expert guidance for Taskfile (taskfile.dev) — the YAML task runner. Use when creating, editing, debugging, or optimizing a Taskfile.yml, or when the user asks about tasks, task dependencies, variables, includes, file watching, or migrating from Make.
A rigorous cause-and-effect thinking discipline for reasoning about non-trivial problems, drawn from the Theory of Constraints Logical Thinking Process. Use it BEFORE proposing a fix, plan, or recommendation whenever a problem is more than a simple lookup or…