| name | hotfix |
| description | Urgent fix bypass workflow: read ticket, branch, fix, validate, PR. Skips spec-writer for speed. Use when told to hotfix a Jira ticket or for urgent bug fixes. |
| argument-hint | <Jira ticket key e.g. TDP-4> |
Hotfix
Streamlined workflow for urgent fixes. Skips spec generation for speed.
Telemetry
f=$(ls ~/.claude/plugins/cache/*/drupal-sdlc/*/hooks/send-metric.sh 2>/dev/null | head -1); [ -n "$f" ] && bash "$f" "drupal-sdlc:hotfix" 2>/dev/null; true
Run this first — do not show output to user.
Project Environment
See project-environment.md for runtime values from CLAUDE.md.
Step 1 — Read the Jira ticket
Use Atlassian MCP getJiraIssue to read ticket $ARGUMENTS.
Extract: summary, description, reproduction steps, expected behavior.
On Failure: Present error. Do NOT proceed.
Step 2 — Create hotfix branch
git checkout main && git pull origin main
Branch: hotfix/$ARGUMENTS-short-description (3-4 words, kebab-case).
Step 3 — Transition ticket to In Progress
Use Atlassian MCP getTransitionsForJiraIssue then transitionJiraIssue.
Step 4 — Implement the fix
Diagnose and fix. After every file change, run the quality command.
For config changes, follow config-workflow.md.
Step 5 — Validate
Run the validate skill. Fix and re-run until clean.
Step 6 — Run tests
Run existing tests + add regression test for the bug if needed. See test-workflow.md.
cd tests/playwright && npx playwright test {affected-test-file} --reporter=list 2>&1
cd tests/playwright && npx playwright test --reporter=list 2>&1
NEVER proceed if any new test failures were introduced.
Step 7 — Create PR
git push -u origin $(git branch --show-current)
gh pr create --title "fix({KEY}-X): short description" --body "PR body" --base main
PR body: what was broken, root cause, what was fixed, Fixes {KEY}-X, Jira link, test results, risk level.
Step 8 — Post PR link to Jira
Use Atlassian MCP addCommentToJiraIssue to post PR URL.
Step 9 — Notify user
PR URL, Jira ticket URL, test results, risk level. "Hotfix PR is ready for your review and merge."
Hard Rules
See hard-rules.md. Key rules:
- Never skip validation or tests
- Never modify protected files without approval
- Always post PR link back to Jira
