with one click
fix
// Structured bug fix workflow — find issue in tracker, root-cause, fix, test, verify, document
// Structured bug fix workflow — find issue in tracker, root-cause, fix, test, verify, document
Scaffold and implement a new MCP tool end-to-end — endpoint, handler, registration, docs
Debug a malfunctioning MCP tool — trace the full request lifecycle to find the issue
Guided npm publish workflow — version bump, quality gate, build, publish, tag
Post-task retrospective — captures what worked, what went wrong, writes lessons to auto-memory
Review code for bugs, MCP protocol violations, consistency issues, and convention adherence
Update documentation after tool changes — TOOLS.md, skill.md, README, INSTALLATION.md
| name | fix |
| description | Structured bug fix workflow — find issue in tracker, root-cause, fix, test, verify, document |
| argument-hint | [ISS-NNN or bug description] |
Fix the bug: $ARGUMENTS
ISSUES.md — find the relevant tracked issue by ID or descriptionISSUES.md first (assign next ISS-NNN ID)IN PROGRESSISSUES.md status to FIXED and stopRun the quality gate immediately after the fix:
npm run typecheck && npm run lint && npm run test -- --passWithNoTests
All must pass. git diff — confirm only intentional changes.
This step is not optional. The fix is incomplete until:
ISSUES.md is updated with:
FIXED with datedocs/TOOLS.md updated if the fix changes tool behaviorCLAUDE.md Known Patterns & Pitfalls updated if the pattern is generalizableIssue: ISS-NNN — [title]
Severity: [level]
Root Cause: [file:line — one sentence]
Status: FIXED
Files changed: [list]
Tests: [added N / updated N / none needed]
Docs updated: [list or "none"]
ISSUES.md — fixes without tracking are invisible