pradeepmouli/speckit-workflows.bugfix
.github/skills/speckit-workflows.bugfix/SKILL.md
Create a bug fix workflow with regression test and minimal documentation.
$ install --global
skillsauthnpx skillsauth add pradeepmouli/lspeasy speckit-workflows.bugfixInstall 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 17, 2026, 7:59 AM4.8s1 file scanned
SKILL.md
- name:
- speckit-workflows.bugfix
- description:
- Create a bug fix workflow with regression test and minimal documentation.
- compatibility:
- Requires spec-kit project structure with .specify/ directory
- author:
- github-spec-kit
- source:
- templates/commands/workflows.bugfix.md
Speckit Workflows.Bugfix Skill
<!-- Extension: workflows --> <!-- Config: .specify/extensions/workflows/ -->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.shfrom 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.mdto 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.
- Extract current behavior, expected behavior, and reproduction steps from description
- Mark severity based on description keywords (crash/data loss = Critical, broken feature = High, etc.)
- Leave root cause analysis empty (to be filled during investigation)
- Leave fix strategy empty (to be filled during planning)
-
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.
Related Skills
pradeepmouli/lsp-refactor
tools
VerifiedTrustedCommunity
Use for ANY rename, file-move, or move-symbol refactor — especially rename-heavy work across multiple files. Claude Code's built-in LSP tool is READ-ONLY (find references, but no rename / file-move / move-symbol). Hand-editing those refactors silently misses re-exports, aliased imports, type-only imports, and {@link} doc references. This skill drives a real language server via the `lspeasy` CLI to apply a correct WorkspaceEdit that catches every reference. Trigger when the user asks to rename a function/class/variable/type project-wide, move a file and fix its importers, or pull a symbol out into another module.
2SKILL.mdUpdated Jun 3, 2026
pradeepmouli/lspeasy-core
tools
VerifiedTrustedCommunity
Documentation site for lspeasy Use when: You are building a browser-based LSP client, a WebSocket-backed language....
2SKILL.mdUpdated Apr 17, 2026
pradeepmouli/lspeasy-client
tools
VerifiedTrustedCommunity
Documentation site for lspeasy Use when: You are implementing a custom client layer and need the same validation....
2SKILL.mdUpdated Apr 17, 2026
pradeepmouli/lspeasy
tools
VerifiedTrustedCommunity
Use when working with lspeasy (client, core, server). Covers: lsp, language-server-protocol, lsp-client, language-client, jsonrpc, transport, lsp-server, language-server.
1SKILL.mdUpdated Apr 25, 2026