.claude/skills/speckit-workflows-bugfix/SKILL.md
Create a bug fix workflow with regression test and minimal documentation.
npx skillsauth add pradeepmouli/zod-to-form speckit-workflows-bugfixInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.bugfix (or /speckit.bugfix) in the triggering message is the bug 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.
Given that bug description, do this:
Run the script .specify/extensions/workflows/scripts/bash/create-bugfix.sh from repo root and parse its JSON output for BUG_ID, BRANCH_NAME, and BUG_REPORT_FILE. 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/bugfix/bug-report-template.md to understand required sections.
Write the bug report to BUG_REPORT_FILE using the template structure, replacing placeholders with concrete details derived from the bug description (arguments) while preserving section order and headings.
Report completion with Next Steps:
Bug fix workflow initialized
**Branch**: [BRANCH_NAME]
**Bug ID**: [BUG_ID]
**Bug Report**: [BUG_REPORT_FILE]
**Next Steps:**
1. Review and investigate the bug
2. Update bug-report.md with root cause analysis
3. Run `/speckit.plan` to create fix plan (include regression test strategy)
4. Run `/speckit.tasks` to break down the fix into tasks
5. Run `/speckit.implement` to execute the fix
**Reminder**: Write regression test BEFORE implementing fix
Note: The script creates and checks out the new branch before writing files.
tools
Use when working with zod-to-form (core, react, cli, codegen, vite).
tools
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.
development
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.
development
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.