Meta-skill workflow orchestrator for bug investigation and resolution. Routes to debug, implement, test, and commit based on scope.

Fix Workflow orchestrator for bug investigation and resolution. Chains specialized skills based on issue scope. Usage Question Flow (No Arguments) If the user types just /fix with no or partial arguments, guide them through this question flow. Use AskUserQuestion for each phase. Phase 0: Workflow Selection Mapping: "Help me choose" → Continue to Phase 1 4 questions "Bug" → Set scope=bug, skip to Phase 2 (issue details) "Hook" → Set scope=hook, skip to Phase 2 (issue details) "Dependencies" → Set scope=deps, skip to Phase 2 (issue details) "PR Comments" → Set scope=pr comments, skip to Phase 2 (issue details) If Answer is Unclear (via "Other"): Phase 1: Issue Type Mapping: "Something broken" → bug scope "Hook not firing" → hook scope "Import errors" → deps scope "PR feedback" → pr comments scope Phase 2: Issue Details Capture the error message, unexpected behavior, or PR link. Phase 3: Investigation Depth Mapping: "Diagnose only" → dry run "Quick fix" → skip investigation, go straight to spark agent Phase 4: Testing & Commit Mapping: No "regression test" → no test No "commit" → no commit Summary Before Execution Scopes Scope Chain Description bug debug implement task test driven development commit General bug fix workflow hook debug hooks hook developer implement task test hook Hook specific debugging deps dependency preflight oracle plan agent implement plan qlty check Dependency issues pr comments github search research codebase plan agent implement plan commit Address PR feedback Options Option Effect no test Skip regression test creation dry run Diagnose only, don't implement fix no commit Don't auto commit the fix Workflow Phase 1: Parse Arguments Phase 2: Investigation (Parallel) Spawn sleuth agent for parallel investigation: Phase 3: Diagnosis Report Present findings to user: Phase 4: Human Checkpoint (Diagnosis) REQUIRED: Wait for user confirmation before implementing. If user says "modify", gather new requirements and update approach. If user says "no", create diagnostic handoff and exit. If dry run , create diagnostic handoff and exit here. Phase 4.5: Risk Assessment (Premortem) After diagnosis approval, before implementation: Run a quick premortem on the proposed fix to catch risks: Context for premortem: Risk Decision: No HIGH tigers : Proceed to implementation HIGH tigers found : Present to user with options: Accept risks and proceed Modify approach to address risks Research mitigation strategies If "Research mitigations", spawn scout + oracle in parallel per risk, then re present options. Phase 5: Implementation Route to appropriate implementation skill based on scope: bug scope: hook scope: deps scope: pr comments scope: Phase 6: Regression Test (unless no test) Phase 7: Human Checkpoint (Verification) If "needs adjustment", gather feedback and return to Phase 5. If "revert", run rollback command and exit. Phase 8: Commit (unless no commit) Chain Details by Scope bug hook deps pr comments Handoff Creation Always create a handoff , even with dry run : Location: thoughts/shared/handoffs/fix/{scope}/{timestamp} {description}.yaml Examples Basic Bug Fix Diagnose Only Fix Without Auto Commit Quick Fix (No Regression Test) Address PR Comments Error Handling Error Action Investigation finds nothing Ask user for more context User rejects diagnosis Refine hypothesis with user input Fix breaks other tests Rollback, refine approach User rejects verification Offer to revert or adjust Commit fails Present error, offer retry Integration with Other Skills This skill orchestrates: debug / debug hooks : Initial investigation sleuth : Parallel investigation agent kraken : TDD implementation agent implement task : Single task implementation test driven development : Test creation plan agent : Complex fix planning dependency preflight : Dependency checks oracle / research codebase : Context gathering github search : PR context fetching qlty check : Quality verification premortem : Risk assessment before implementation commit : Git commit workflow create handoff : Session handoff Checkpoints Summary Checkpoint Purpose Skip Condition After diagnosis Confirm root cause Never skip After premortem Accept or mitigate risks No HIGH tigers After fix Verify resolution Never skip Before commit Review changes no commit The human checkpoints are critical for: 1. Preventing wrong fixes from being implemented 2. Ensuring user understands what changed 3. Catching edge cases only humans notice