Fix Issue

Systematic issue resolution with hypothesis-based root cause analysis, similar issue detection, and prevention recommendations.

Quick Start

/ork:fix-issue 123
/ork:fix-issue 456

Opus 4.6: Root cause analysis uses native adaptive thinking. Dynamic token budgets scale with context window for thorough investigation.

STEP 0: Verify User Intent

BEFORE creating tasks, clarify fix approach using AskUserQuestion. See rules/evidence-gathering.md for the full prompt template and workflow adjustments per approach (Proper fix, Quick fix, Investigate first, Hotfix).

STEP 0b: Select Orchestration Mode

Choose Agent Teams (mesh) or Task tool (star). See references/agent-selection.md for the selection criteria, cost comparison, and task creation patterns.

Workflow Overview

Phase	Activities	Output
1. Understand Issue	Read GitHub issue details	Problem statement
2. Similar Issue Detection	Search for related past issues	Related issues list
3. Hypothesis Formation	Form hypotheses with confidence scores	Ranked hypotheses
4. Root Cause Analysis	5 parallel agents investigate	Confirmed root cause
5. Fix Design	Design approach based on RCA	Fix specification
6. Implementation	Apply fix with tests	Working code
7. Validation	Verify fix resolves issue	Evidence
8. Prevention	How to prevent recurrence	Prevention plan
9. Runbook	Create/update runbook entry	Runbook
10. Lessons Learned	Capture knowledge	Persisted learnings
11. Commit and PR	Create PR with fix	Merged PR

Full phase details: See references/fix-phases.md for bash commands, templates, and procedures for each phase.

Critical Constraints

Feature branch MANDATORY -- NEVER commit directly to main or dev
Regression test MANDATORY -- write failing test BEFORE implementing fix
Prevention required -- at least one of: automated test, validation rule, or process check
Make minimal, focused changes; DO NOT over-engineer

CC 2.1.49 Enhancements

See references/cc-enhancements.md for session resume, task metrics, tool guidance, worktree isolation, and adaptive thinking.

Rules Quick Reference

Rule	Impact	What It Covers
evidence-gathering	HIGH	User intent verification, confidence scale, key decisions
rca-five-whys	HIGH	5 Whys iterative causal analysis
rca-fishbone	MEDIUM	Ishikawa diagram, multi-factor analysis
rca-fault-tree	MEDIUM	Fault tree analysis, AND/OR gates, critical systems

Related Skills

ork:commit - Commit issue fixes
debug-investigator - Debug complex issues
ork:issue-progress-tracking - Auto-updates from commits
ork:remember - Store lessons learned

References

Version: 2.1.0 (February 2026)