The slash commands you'll use daily
A slash command is a pre-packaged multi-step prompt. The chowly bundle gives you six commands that, chained, take a ticket from "To Do" to "In Review."
The pipeline
| Step | Command | What it does |
|---|---|---|
| 1 | /chowly:implement_jira TEAM-XXXX | Pull ticket → rename branch → plan → execute |
| 2 | /chowly:write_specs | Cover diff with specs, run suite |
| 3 | /chowly:fix_specs | If specs fail, iterate to green |
| 4 | /chowly:cleanup | Senior Engineering Mentor pass over the diff |
| 5 | /chowly:code_review | Self-review against CODE_REVIEW.md |
| 6 | /chowly:request_review | Open PR, set reviewer, transition ticket |
Each one, briefly
/chowly:implement_jira TEAM-XXXXX
The entry point. Loads the jira skill, spawns the Software Engineer agent, hands it the ticket key. The agent looks up the ticket via the Atlassian MCP, renames the branch to feature/TEAM-XXXXX_short_desc, transitions the ticket to In Progress, researches the code, and presents a plan. After you approve, it executes.
/chowly:write_specs
Spawns the Automation Testing Engineer agent. It diffs your branch against development, identifies uncovered code, writes specs in your project's idiom, and runs the suite. If specs fail, it iterates. You can override with style notes ("stub at the service level, not webmock").
/chowly:fix_specs
Targeted at "specs are failing, fix them." Use after a refactor, a CI failure, or a long implementation. The agent diagnoses each failure and applies the right fix — sometimes the spec, sometimes the code. It explains its diagnosis before changing anything.
/chowly:cleanup
Spawns the Senior Engineering Mentor agent. It scans the diff for DRY/SRP/verbosity/convention issues and presents findings as a markdown table. You approve item by item, or all, or none. Then it refactors and runs rubocop and the affected specs.
/chowly:code_review
Reads your repo's CODE_REVIEW.md, walks the diff against the checklist, writes a markdown review to tmp/<date>-CODE-REVIEW.md. Treat the output as a draft peer review — fix what's real, push back on what isn't, ignore false positives.
/chowly:request_review
The "ship it" command. Pushes the branch, opens a PR against development, reads the Jira Reviewer field, sets the GitHub reviewer, transitions the ticket to In Review. Plus a clean PR description with Summary and Test plan sections.
Why these instead of typing the steps yourself
Three reasons:
- They encode the team's process. The right way to ship is a one-liner. New team members do it right by default.
- They cap variance. Without commands, every developer improvises. With them, behavior converges.
- They make Claude predictable. When you type
/chowly:implement_jira, you know the first thing Claude does is pull the ticket and rename the branch. That predictability is what lets you trust it.