Menu
Create an emergency hotfix workflow with expedited process and mandatory post-mortem.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Review a production UX checkout harness run against the deployed Studio (daikonic). Use after `pnpm --filter @rune-langium/studio run test:prod-ux` (or test:prod-smoke) completes, when the user asks to review/triage a prod checkout run, or when a nightly prod-ux artifact needs auditing. Consumes report/run-manifest.json + screenshots + traces and produces a severity-ranked UX review with per-journey verdicts.
Documentation site and generated agent skills for rune-langium APIs
Documentation site and generated agent skills for rune-langium APIs Use when: Validating a single `.rosetta` file or snippet in memory.
Documentation site and generated agent skills for rune-langium APIs Use when: Embedding a Rune DSL language server in a web application via WebSocket.
Documentation site and generated agent skills for rune-langium APIs Use when: Rendering two or more `RuneTypeGraph` components simultaneously (different....
Runtime <ZodForm> renderer for Zod v4 schemas Use when: You need form rendering in storybook, playgrounds, or low-traffic admin UIs —.... Also: zod, zod-v4, react, forms, form-generation, react-hook-form, schema-driven, dynamic-forms, form-renderer, hookform-resolver, zod-form-renderer.
| name | speckit-workflows-hotfix |
| description | Create an emergency hotfix workflow with expedited process and mandatory post-mortem. |
| compatibility | Requires spec-kit project structure with .specify/ directory |
| metadata | {"author":"github-spec-kit","source":"workflows:commands/hotfix.md"} |
The user input to you can be provided directly by the agent or as a command argument - you MUST consider it before proceeding with the prompt (if not empty).
User input:
$ARGUMENTS
The text the user typed after /speckit.workflows.hotfix (or /speckit.hotfix) in the triggering message is the incident description. Assume you always have it available in this conversation even if $ARGUMENTS appears literally below. Do not ask the user to repeat it unless they provided an empty command.
EMERGENCY WORKFLOW - EXPEDITED PROCESS
Given that incident description, do this:
Run the script .specify/extensions/workflows/scripts/bash/create-hotfix.sh --json "$ARGUMENTS" from repo root and parse its JSON output for HOTFIX_ID, BRANCH_NAME, HOTFIX_FILE, POSTMORTEM_FILE, and TIMESTAMP. All file paths must be absolute.
IMPORTANT You must only ever run this script once. The JSON is provided in the terminal as output - always refer to it to get the actual content you're looking for.
Load .specify/extensions/workflows/templates/hotfix/hotfix-template.md to understand required sections.
Write the hotfix incident log to HOTFIX_FILE using the template structure:
Report completion with Next Steps:
HOTFIX WORKFLOW INITIATED (EXPEDITED)
**Hotfix ID**: [HOTFIX_ID]
**Branch**: [BRANCH_NAME]
**Incident Time**: [TIMESTAMP]
**Severity**: [P0/P1/P2]
**Hotfix Report**: [HOTFIX_FILE]
**Next Steps (URGENT):**
1. Review incident details and confirm severity
2. Notify stakeholders of incident status
3. Run `/speckit.plan` to create expedited fix plan
4. Run `/speckit.tasks` to create minimal task breakdown
5. Run `/speckit.implement` to apply hotfix immediately
**Post-Deployment:**
- Monitor production after deployment
- Schedule post-mortem within 24-48 hours
- Create follow-up `/speckit.bugfix` for proper fix with tests
**Note**: This is the ONLY workflow that permits test-after approach due to emergency
Note: Hotfix workflow bypasses normal TDD process due to emergency nature. Tests must be added AFTER fix is deployed. This is the ONLY workflow that permits this deviation from the constitution.