Skip to content

Commit 3d0e2ea

Browse files
cahaselerclaude
cahaseler
and
claude
committed
feat: add /cc-track:fix-issues command for structured issue triage
Adds new command that walks through code review issues one-by-one with Fix/Defer/Dismiss/Discuss options. Key features: - "Just Fix It" protocol auto-fixes trivial issues before triage - Always provides recommended action with reasoning - Uses TodoWrite to track triage and fix progress - Prefers subagents for investigation and straightforward fixes - Creates issue-log.md in spec folder as permanent audit trail - Iterative-safe: re-running filters already-handled issues Also updates: - prepare-completion.md to route >1 issues to fix-issues command - 8 review agents with pre-report deduplication awareness - cc-track-workflow.md with new command documentation Closes #172 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1 parent abc2b69 commit 3d0e2ea

11 files changed

+526
-41
lines changed

‎.cc-track/cc-track-workflow.md‎

Lines changed: 36 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,11 @@
77
The cc-track system follows a structured, command-driven workflow that separates requirements from implementation:
88

99
```
10-
/cc-track:specify → /cc-track:plan → /cc-track:tasks → Implementation → /cc-track:prepare-completion → /cc-track:complete-task → PR → Merge
10+
/cc-track:specify → /cc-track:plan → /cc-track:tasks → Implementation → /cc-track:prepare-completion → [/cc-track:fix-issues] → /cc-track:complete-task → PR → Merge
1111
```
1212

13+
Note: `/cc-track:fix-issues` is automatically invoked by `prepare-completion` when >1 issues are found.
14+
1315
Each command prompts for the next step, creating a natural flow through the development process.
1416

1517
---
@@ -182,10 +184,43 @@ This discretionary approach means simple features don't waste time on exploratio
182184

183185
**Result:** Clear pass/fail with specific fix instructions
184186

187+
**Routing based on issue count:**
188+
- **0 issues:** "Ready for completion" - proceed to `/cc-track:complete-task`
189+
- **1 issue:** Presented inline for quick decision
190+
- **>1 issues:** Automatically invokes `/cc-track:fix-issues` for structured triage
191+
185192
**Next step:** Fix any issues, update docs, then run `/cc-track:complete-task`
186193

187194
---
188195

196+
### 5b. `/cc-track:fix-issues` - Triage Review Issues
197+
198+
**Purpose:** Walk through code review issues one-by-one with structured decision options
199+
200+
**When invoked:**
201+
- Automatically by `/cc-track:prepare-completion` when >1 validated issues found
202+
- Can be invoked directly if issues exist in conversation context
203+
204+
**What happens:**
205+
1. Creates `issue-log.md` in spec folder with all issues (or updates existing)
206+
2. Checks existing `issue-log.md` and `backlog.md` to filter already-handled issues
207+
3. Presents each NEW issue (highest score first) with options:
208+
- **Fix** - Add to immediate fix list
209+
- **Defer** - Add to backlog for future work
210+
- **Dismiss** - False positive or acceptable as-is
211+
- **Discuss** - Investigate before deciding
212+
4. After all issues triaged, shows action summary
213+
5. Executes fixes in order (only after full triage complete)
214+
6. Reminds to re-run `/cc-track:prepare-completion` to verify
215+
216+
**Issue-log.md location:** `.cc-track/specs/{active-spec}/issue-log.md`
217+
218+
**Iterative safe:** Re-running filters out already-handled issues from previous triage runs
219+
220+
**Result:** Documented triage decisions, fixes implemented, issue-log.md as permanent audit trail
221+
222+
---
223+
189224
### 6. `/cc-track:complete-task` - Finalize and Create PR
190225

191226
**Purpose:** Mark task complete, squash commits, create PR

‎agents/bug-scanner.md‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -118,6 +118,22 @@ For every high-risk location, check:
118118

119119
Report all potential issues found - a separate scoring agent will validate each one. Do not filter based on your confidence level or attempt to rate importance.
120120

121+
## Pre-Report Deduplication
122+
123+
Before finalizing your report, check for already-handled issues to avoid reporting duplicates:
124+
125+
1. **Check for existing files** in the spec folder (if they exist):
126+
- `{spec_folder}/issue-log.md` - Contains issues already triaged (Fixed/Dismissed/Deferred)
127+
- `.cc-track/backlog.md` - Contains deferred items from previous triage runs
128+
129+
2. **Filter your findings:**
130+
- Remove any issue that matches a "Fixed" or "Dismissed" entry in issue-log.md (match by location)
131+
- Remove any issue that matches a "Deferred" entry in backlog.md (match by location or description)
132+
- Only report NEW issues not yet handled
133+
134+
3. **Note in your report** if issues were filtered:
135+
- Add a line like: "Note: X issues filtered (already in issue-log/backlog)"
136+
121137
## Output Format
122138

123139
**IMPORTANT:** Do NOT score issues yourself. Output a structured list of potential issues. A separate scoring agent will validate each one.

‎agents/comment-compliance-reviewer.md‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -99,6 +99,22 @@ For every comment found:
9999
- Should TODOs be converted to tracked issues?
100100
- Are FIXMEs actually fixed?
101101

102+
## Pre-Report Deduplication
103+
104+
Before finalizing your report, check for already-handled issues to avoid reporting duplicates:
105+
106+
1. **Check for existing files** in the spec folder (if they exist):
107+
- `{spec_folder}/issue-log.md` - Contains issues already triaged (Fixed/Dismissed/Deferred)
108+
- `.cc-track/backlog.md` - Contains deferred items from previous triage runs
109+
110+
2. **Filter your findings:**
111+
- Remove any issue that matches a "Fixed" or "Dismissed" entry in issue-log.md (match by location)
112+
- Remove any issue that matches a "Deferred" entry in backlog.md (match by location or description)
113+
- Only report NEW issues not yet handled
114+
115+
3. **Note in your report** if issues were filtered:
116+
- Add a line like: "Note: X issues filtered (already in issue-log/backlog)"
117+
102118
## Output Format
103119

104120
**IMPORTANT:** Do NOT score issues yourself. Output a structured list of potential issues. A separate scoring agent will validate each one.

‎agents/dead-code-detector.md‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -130,6 +130,22 @@ When code moves from A to B, verify:
130130
- Documentation references B, not A
131131
- No config still points to A
132132

133+
## Pre-Report Deduplication
134+
135+
Before finalizing your report, check for already-handled issues to avoid reporting duplicates:
136+
137+
1. **Check for existing files** in the spec folder (if they exist):
138+
- `{spec_folder}/issue-log.md` - Contains issues already triaged (Fixed/Dismissed/Deferred)
139+
- `.cc-track/backlog.md` - Contains deferred items from previous triage runs
140+
141+
2. **Filter your findings:**
142+
- Remove any issue that matches a "Fixed" or "Dismissed" entry in issue-log.md (match by location)
143+
- Remove any issue that matches a "Deferred" entry in backlog.md (match by location or description)
144+
- Only report NEW issues not yet handled
145+
146+
3. **Note in your report** if issues were filtered:
147+
- Add a line like: "Note: X issues filtered (already in issue-log/backlog)"
148+
133149
## Output Format
134150

135151
**IMPORTANT:** Do NOT score issues yourself. Output a structured list of potential dead code findings. A separate scoring agent will validate each one.

‎agents/duplication-detector.md‎

Lines changed: 16 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -99,11 +99,25 @@ Review package.json for libraries that might provide:
9999
- Similar functionality with better testing/maintenance
100100
- Industry-standard solutions
101101

102-
## Output Format
102+
## Pre-Report Deduplication
103103

104-
**IMPORTANT:** Do NOT score issues yourself. Output a structured list of potential issues. A separate scoring agent will validate each one.
104+
Before finalizing your report, check for already-handled issues to avoid reporting duplicates:
105+
106+
1. **Check for existing files** in the spec folder (if they exist):
107+
- `{spec_folder}/issue-log.md` - Contains issues already triaged (Fixed/Dismissed/Deferred)
108+
- `.cc-track/backlog.md` - Contains deferred items from previous triage runs
109+
110+
2. **Filter your findings:**
111+
- Remove any issue that matches a "Fixed" or "Dismissed" entry in issue-log.md (match by location)
112+
- Remove any issue that matches a "Deferred" entry in backlog.md (match by location or description)
113+
- Only report NEW issues not yet handled
105114

115+
3. **Note in your report** if issues were filtered:
116+
- Add a line like: "Note: X issues filtered (already in issue-log/backlog)"
106117

118+
## Output Format
119+
120+
**IMPORTANT:** Do NOT score issues yourself. Output a structured list of potential issues. A separate scoring agent will validate each one.
107121

108122
```markdown
109123
# Duplication Detection Report

‎agents/guidelines-reviewer.md‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -114,6 +114,22 @@ For each guideline found:
114114
3. Check complexity limits aren't exceeded
115115
4. Verify prohibited patterns aren't used
116116

117+
## Pre-Report Deduplication
118+
119+
Before finalizing your report, check for already-handled issues to avoid reporting duplicates:
120+
121+
1. **Check for existing files** in the spec folder (if they exist):
122+
- `{spec_folder}/issue-log.md` - Contains issues already triaged (Fixed/Dismissed/Deferred)
123+
- `.cc-track/backlog.md` - Contains deferred items from previous triage runs
124+
125+
2. **Filter your findings:**
126+
- Remove any issue that matches a "Fixed" or "Dismissed" entry in issue-log.md (match by location)
127+
- Remove any issue that matches a "Deferred" entry in backlog.md (match by location or description)
128+
- Only report NEW issues not yet handled
129+
130+
3. **Note in your report** if issues were filtered:
131+
- Add a line like: "Note: X issues filtered (already in issue-log/backlog)"
132+
117133
## Scoring Process
118134

119135
**IMPORTANT:** Do NOT score issues yourself. Output a structured list of potential issues. A separate scoring agent will validate each one.

‎agents/plan-adherence-reviewer.md‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -87,6 +87,22 @@ For each technical decision in plan.md:
8787
4. Confirm API contracts are implemented correctly
8888
5. Note deviations from planned structure
8989

90+
## Pre-Report Deduplication
91+
92+
Before finalizing your report, check for already-handled issues to avoid reporting duplicates:
93+
94+
1. **Check for existing files** in the spec folder (if they exist):
95+
- `{spec_folder}/issue-log.md` - Contains issues already triaged (Fixed/Dismissed/Deferred)
96+
- `.cc-track/backlog.md` - Contains deferred items from previous triage runs
97+
98+
2. **Filter your findings:**
99+
- Remove any issue that matches a "Fixed" or "Dismissed" entry in issue-log.md (match by location)
100+
- Remove any issue that matches a "Deferred" entry in backlog.md (match by location or description)
101+
- Only report NEW issues not yet handled
102+
103+
3. **Note in your report** if issues were filtered:
104+
- Add a line like: "Note: X issues filtered (already in issue-log/backlog)"
105+
90106
## Output Format
91107

92108
**IMPORTANT:** Do NOT score issues yourself. Output a structured list of potential issues. A separate scoring agent will validate each one.

‎agents/spec-compliance-reviewer.md‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -84,6 +84,22 @@ For each requirement in spec.md:
8484
3. Check edge cases mentioned in spec are handled
8585
4. Note any gaps or partial implementations
8686

87+
## Pre-Report Deduplication
88+
89+
Before finalizing your report, check for already-handled issues to avoid reporting duplicates:
90+
91+
1. **Check for existing files** in the spec folder (if they exist):
92+
- `{spec_folder}/issue-log.md` - Contains issues already triaged (Fixed/Dismissed/Deferred)
93+
- `.cc-track/backlog.md` - Contains deferred items from previous triage runs
94+
95+
2. **Filter your findings:**
96+
- Remove any issue that matches a "Fixed" or "Dismissed" entry in issue-log.md (match by location)
97+
- Remove any issue that matches a "Deferred" entry in backlog.md (match by location or description)
98+
- Only report NEW issues not yet handled
99+
100+
3. **Note in your report** if issues were filtered:
101+
- Add a line like: "Note: X issues filtered (already in issue-log/backlog)"
102+
87103
## Output Format
88104

89105
**IMPORTANT:** Do NOT score issues yourself. Output a structured list of potential issues. A separate scoring agent will validate each one.

‎agents/task-completion-reviewer.md‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -91,6 +91,22 @@ For each task in tasks.md:
9191
3. Check that related tests exist (if TDD was specified)
9292
4. Note any tasks that appear incomplete or missing
9393

94+
## Pre-Report Deduplication
95+
96+
Before finalizing your report, check for already-handled issues to avoid reporting duplicates:
97+
98+
1. **Check for existing files** in the spec folder (if they exist):
99+
- `{spec_folder}/issue-log.md` - Contains issues already triaged (Fixed/Dismissed/Deferred)
100+
- `.cc-track/backlog.md` - Contains deferred items from previous triage runs
101+
102+
2. **Filter your findings:**
103+
- Remove any issue that matches a "Fixed" or "Dismissed" entry in issue-log.md (match by location)
104+
- Remove any issue that matches a "Deferred" entry in backlog.md (match by location or description)
105+
- Only report NEW issues not yet handled
106+
107+
3. **Note in your report** if issues were filtered:
108+
- Add a line like: "Note: X issues filtered (already in issue-log/backlog)"
109+
94110
## Output Format
95111

96112
**IMPORTANT:** Do NOT score issues yourself. Output a structured list of potential issues. A separate scoring agent will validate each one.

0 commit comments

Comments
 (0)