Agent Claude Code
Read-only code reviewer with a fresh context. Use for /review, before /commit on a risky change, or when you want a second opinion that hasn't seen your reasoning. Returns concrete findings; never edits.
Command Claude Code
A focused pipeline: understand the change, hold it to the four quality dimensions, fix the safe stuff, then commit with a clean message. No ceremony — no ticket lookup, no metrics.
Command Claude Code
The rest of the workflow covers the happy path. This is for when something is broken, which is most days. It exists because debugging is where an assistant most reliably goes wrong: it reads the symptom, pattern-matches a plausible cause, changes something, and the symptom disappears for a reason nobody understands.
Command Claude Code needs its repo
Run this when you're starting anything non-trivial. The goal: leave with a clear, scoped plan, an entry in TASKS.md, and a feature branch — ready to code. Don't write the feature itself here; just set it up.
Command Claude Code
A second pair of eyes on the code you just wrote, before /commit. The risk in solo work is that nobody else ever reads the diff — this command is that reader. Output is a concrete findings list; you decide what to fix.
Command Claude Code
Run this once, right after installing. Everything else in the workflow reads the Project context block — /test needs to know your test runner, /commit needs your lint command, /ship needs your base branch. Left blank, every command guesses, and a guess that's wrong is worse than a question.
Command Claude Code
Even solo, a PR is worth it: it runs CI, gives a clean diff to skim before merging, and leaves a durable record. This uses the gh CLI.
Command Claude Code
Add the test that would have caught the bug, or that locks in the new behavior. Match the project's existing testing setup — don't introduce a new framework.
Command Claude Code needs its repo
/test proves the assertions you wrote are satisfied. This proves the software does what the task asked. They fail differently: a test suite can be entirely green while the button doesn't render, the endpoint 500s on the real payload, or the CLI prints the wrong thing.
Command Claude Code
The lightweight end-of-task ritual that replaces a ticket system. Leaves a durable trail in two committed files — no external service, no time accounting.
Command Claude Code
You are a Senior Tech Lead, checking code conventions and AI quality scoring for the $PROJECTNAME project.
Command Claude Code
You are $DEVROLE, creating a new branch for the $PROJECTNAME project with a Jira ticket ID.
Command Claude Code
You are an assistant that creates Jira tasks for the $PROJECTNAME project. Do NOT ask again for information the user has already provided.
Command Claude Code
Open a GitHub PR for acme-mono with a CI-checked PROJ-prefixed title, using a classic PAT.
Command Claude Code
You are $DEVROLE, writing unit tests for the $PROJECTNAME project.
Command Claude Code
You are an assistant that creates a Daily Report in a text-ready format for the Acme project — suitable for the daily stand-up (16:00 Vietnam / 10:00 Portugal) and the Slack daily update.
Command Claude Code
You are the assistant that logs work to Jira for the PROJ tickets worked on during the day in the Acme project (single Jira project: PROJ at your-domain.atlassian.net).
Command Claude Code
Push code, automatically run /commit if not yet committed, compute elapsed time and log work to Jira accurately. Handles all edge cases: no-ticket, no-state, re-push, multi-task, duplicate worklog, corrupt state, negative elapsed, wrong commit author.
Command Claude Code
You are a Senior Tech Lead reviewing uncommitted code for the $PROJECTNAME project. Review from 3 independent perspectives (Logic / Design / Security+UX). The output is a findings list for the user to decide what to fix.
Command Claude Code
Senior Tech Lead review of a GitHub PR in acme-mono — real quality, no gaming.
Command Claude Code
You are $DEVROLE, performing code refactoring to increase the AI quality score.
Command Claude Code
You are $DEVROLE, starting the workflow for a new task in the $PROJECTNAME project.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: