메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| 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> |
Streamlined workflow for urgent fixes. Skips spec generation for speed.
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.
See project-environment.md for runtime values from CLAUDE.md.
Use Atlassian MCP getJiraIssue to read ticket $ARGUMENTS.
Extract: summary, description, reproduction steps, expected behavior.
On Failure: Present error. Do NOT proceed.
git checkout main && git pull origin main
Branch: hotfix/$ARGUMENTS-short-description (3-4 words, kebab-case).
Use Atlassian MCP getTransitionsForJiraIssue then transitionJiraIssue.
Diagnose and fix. After every file change, run the quality command.
For config changes, follow config-workflow.md.
Run the validate skill. Fix and re-run until clean.
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.
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.
Use Atlassian MCP addCommentToJiraIssue to post PR URL.
PR URL, Jira ticket URL, test results, risk level. "Hotfix PR is ready for your review and merge."
See hard-rules.md. Key rules:
Fix PHPStan, PHPCS, twigcs, and yamllint violations from error output. Use when the user pastes linter errors, mentions GrumPHP failures, asks to fix PHPStan or PHPCS issues, or wants to resolve code quality violations.
Generate Drupal config YAML files from plain English descriptions. Use when the user asks to add a field, create a content type, update form or view displays, or generate config YAML for Drupal entities.
Generate complete Drupal custom module boilerplate, especially for API integrations. Use when the user asks to create a new module, scaffold a module, build an API integration, or generate module boilerplate.
Run post-install setup for the drupal-sdlc plugin. Auto-detects project values, verifies gh CLI and MCP connectivity. Use after installing the plugin on a new project, or when MCPs show as failed.
Create a pull request from completed work. Generates PR title, description, what changed, test plan, and risk level. Always run the validate skill before using this.
Review a PR diff and flag risks, run security checklist, verify AC coverage, and score risk level. Use this before merging any PR.