dotfiles

Author a teach workspace's lessons/reference/index in markdown and build both the browsable HTML site and a phone-friendly EPUB from that one source.

A relentless interview that asks every frontier question at once, round by round.

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.

Print the relevant text as raw copy-able markdown and copy it to the clipboard. Run `/markdown file` to copy it as a file reference instead, for pasting into Slack.

Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

Implement a piece of work based on a spec or set of tickets.

Commit staged git changes, or include current changes only when the user explicitly says /commit all or $commit all. Use when asked to commit, create a commit, or finalize changes.

Consult a higher-level model about the current activity.

Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.

A relentless interview to sharpen a plan or design.

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

Compact the current conversation into a handoff document for another agent to pick up.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

Run interactive staged vim.pack.update() + security audit, then review findings before explicit approve/abort.

Use when you need to resolve an in-progress git merge/rebase conflict.

Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Teach the user a new skill or concept, within this workspace.

Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

Verify changed files after completing a task or before commit using cheap targeted checks. Use for staged, commit-all, or working-changes verification when handing work back or when another skill needs changed-file checks.

Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.

Automate browser interactions, test web pages and work with Playwright tests.

Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.

How to write bash scripts. Use when editing bash scripts.

How to use the Chakra component library for React. Use when working on a React+Chakra codebase.

How to use React. Use when working on a React codebase.

How to use Vitest. Use when writing or reviewing Vitest tests.

Use for project task tracking, dependency management, and multi-session handoff with Beads. Trigger when the user explicitly asks for Beads/task tracking, when a side-quest/follow-up issue is identified (offer to create it in Beads), or when finalizing a plan so plan tasks are tracked in Beads.

How to use the gopls MCP for analyzing Go code. Use when working on a Go codebase.

Turn the current conversation context into a PRD and publish it to beads as an epic with subtasks. Use when user wants to create a PRD from the current context.

Do a retrospective of this session so we can learn and improve next time. Triggered when the user asks for a retrospective.

Update CHANGELOG.md with the changes for the next version. Use when asked to update the changelog

Ultra-compressed communication mode. Cuts token usage by speaking like a caveman. Use when user says "caveman mode" or invokes /caveman.