/quick-fix
Ship a small change — a typo, a lint violation, a config tweak — through a branch and PR without the overhead of creating a ticket first.
When to use it
Some changes are too small to deserve ticket ceremony. A misspelling in a doc. A linter rule that needs adjusting. A typo in a config file caught during unrelated work. Writing a Definition-of-Ready ticket for each of those would slow you down without adding safety.
/quick-fix is the escape valve. You still branch, still open a PR,
still need it reviewed and merged — the safety boundaries that matter
stay in force. What you skip is the board ceremony: no Backlog entry,
no Ready promotion, no In Progress move.
Use it when the change is under ~20 lines, doesn’t alter user-visible
behavior, and there’s no existing ticket it would fit under. If the
change is bigger than that, or if it touches behavior, use
/work-ticket instead — the ticket is cheap
insurance that the scope is clear and the test plan is captured.
How it fits
No board state, no ticket. Just branch, PR, merge.
What it does (quick)
- Creates a
fix/<short-description>orcontent/<short-description>branch frommain - Applies the change directly
- Runs lint and tests locally — same gate as
/work-ticket - Opens a PR with “Quick fix — no linked ticket” framing in the body
- Does NOT move any board items (there’s no ticket to move)
- Does NOT guess which existing ticket this corresponds to — if unsure, asks first
Related commands
/work-ticket— the full-ceremony sibling for changes worth a Definition-of-Ready ticket/review-pr— same review path as any other PR
Canonical spec: .claude/commands/quick-fix.md