pradeepmouli/speckit-workflows-hotfix
.agents/skills/speckit-workflows-hotfix/SKILL.md
Create an emergency hotfix workflow with expedited process and mandatory post-mortem.
$ install --global
skillsauthnpx skillsauth add pradeepmouli/zod-to-form speckit-workflows-hotfixInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 29, 2026, 11:39 PM6.8s1 file scanned
SKILL.md
- name:
- speckit-workflows-hotfix
- description:
- Create an emergency hotfix workflow with expedited process and mandatory
- compatibility:
- Requires spec-kit project structure with .specify/ directory
- 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.mdto understand required sections. -
Write the hotfix incident log to HOTFIX_FILE using the template structure:
- Fill incident timeline with TIMESTAMP from script output
- Assess severity from description (P0 = service down, P1 = major feature broken, P2 = workaround available)
- Describe the incident clearly
- Leave "Immediate Fix Applied" section empty (to be filled during planning)
- Leave root cause analysis preliminary (to be refined)
- Document impact assessment from description
-
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.
Related Skills
pradeepmouli/zod-to-form
tools
VerifiedTrustedCommunity
Use when working with zod-to-form (core, react, cli, codegen, vite).
1SKILL.mdUpdated May 10, 2026
pradeepmouli/zod-to-form-vite
tools
VerifiedTrustedCommunity
Vite plugin for zod-to-form — transforms ?z2f imports into generated form components and optionally replaces <ZodForm> JSX call sites with generated components at build time Use when: You want `import SignupForm from './signup.schema?z2f'` to Just Work in a.... Also: vite, vite-plugin, zod, zod-v4, codegen, forms, form-generation, schema-driven, react-hook-form, build-plugin, jsx-transform.
1SKILL.mdUpdated Apr 20, 2026
pradeepmouli/zod-to-form-react
development
VerifiedTrustedCommunity
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.
1SKILL.mdUpdated Apr 20, 2026
pradeepmouli/zod-to-form-core
development
VerifiedTrustedCommunity
Schema walker and processor registry for Zod v4 form generation Use when: You want per-field validation instead of whole-form validation. Also: zod, zod-v4, forms, form-generation, schema, schema-walker, processor-registry, react-hook-form, schema-driven, form-schema, zod-registry.
1SKILL.mdUpdated Apr 20, 2026