SuperMatt

Skills

39 in the Claude listing

• Ask supermattAsk which skill or flow fits your situation.
• Code reviewReview the changes since a fixed point (commit, branch, tag, or merge-base) along three axes: Standards (does the code follow this repo's documented coding standards?), Spec (does the code match what
• Codebase designShared vocabulary for designing deep modules.
• commitCommit all changes on the current branch, main included.
• Dependency vettingVerify a package or tool is authentic before installing, adding, upgrading, or recommending it.
• Diagnosing bugsDiagnosis loop for hard bugs and performance regressions.
• Domain modelingBuild and sharpen a project's domain model.
• Fix findingsApply every finding from the most recent review, audit, verification, or check in this session.
• Grill meA relentless interview to sharpen a plan or design.
• Grill with docsA relentless interview to sharpen a plan or design, which also creates docs (ADRs and glossary) as we go.
• grillingGrill the user relentlessly about a plan, decision, or idea.
• handoffWrite the current conversation into a portable handoff document for another agent to pick up.
• ideateGenerate grounded ideas for what to build next, critique every one, and rank the survivors in a Markdown file.
• implementImplement a piece of work based on a spec, tickets, or triaged issues.
• Implement specImplement a whole spec through parallel ticket worktrees on one integration branch.
• Improve architectureAssess a codebase's architecture, stop when it is healthy, otherwise find deepening opportunities, design the chosen one, and hand a plan to /implement.
• Improve file structureAssess project file organization and prepare a behavior-preserving migration plan for /implement when reorganization is justified.
• Improve testsCut a test suite to the tests that catch real bugs and its run time to the minimum: measure first, delete or demote low-value tests, fix slow setup, and prove every cut keeps the checks that matter.
• juryPut a question or decision to a jury of 3 or 5 subagents: blind independent votes, one anonymized review round, and one committed verdict with the vote, the dissent, and the first action.
• orchestrateWork through GitHub issues or local Markdown tickets unattended in parallel lanes, with workers in Herdr panes and git worktrees.
• prThe shape of a pull request body: a summary diagram, before/after evidence, and merge danger.
• prototypeBuild a throwaway prototype to answer a design question.
• qaQA a change in the running program, the way its user meets it: drive a CLI or terminal UI through tmux, a web app through a browser, and check every requested behavior against what you observe.
• refactorRefactor code at method, file, or project scope.
• researchInvestigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo.
• Resolving merge conflictsResolves an in-progress git merge or rebase conflict by tracing why each side changed, reconciling every conflicted hunk, running the project's checks, and finishing the merge or rebase.
• retroConduct a retrospective on a coding session.
• Setup supermatt skillsConfigure this repo for the engineering skills: set up its issue tracker, triage labels, domain doc layout, and external peer policy.
• Ship prCommit, push, open a pull request, repair CI within bounded attempts, then squash merge and verify post-merge workflows.
• tddTest-driven development.
• teachTeach the user a new skill or concept, within this workspace.
• To questionnaireTurn a decision you can't fully answer into a questionnaire for someone else to fill in.
• To specTurn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
• To ticketsBreak 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 locall
• triageMove issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
• Wait whatStop.
• wayfinderPlan 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.
• What would you doExplain the question you just asked and recommend an answer, with the case for and against each option.
• Writing for agentsWriting documents for agents.