Skill Library

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/spec asked for?).

Shared vocabulary for designing deep modules.

Diagnosis loop for hard bugs and performance regressions.

Build and sharpen a project's domain model.

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

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

Build a throwaway prototype to answer a design question.

You need to resolve an in-progress git merge/rebase conflict.

Keep a reviewable decision trail for long-running or unattended work. A TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result.

Test-driven development.

Writing documents for agents.

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.

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

Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo.

Cut AI tells from any writing. Must always apply.

Stop. That last message did not land. Re-pitch it.

Ask which skill or flow fits your situation. A router over the skills in this repo.

Restate the last message in plain human language, with no jargon.

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

Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax.

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.

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).

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

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.

Generate an interactive bash wizard that walks a human through steps only they can perform.

Create Gmail filters with the `gws` CLI: rules that label, archive, star, or forward mail as it arrives.

Triage Gmail with the `gws` CLI: classify inbox threads into labels, create labels on demand, and bulk-file the results of a mailbox-wide search.