Prompt file imported from grimm00/work-prod (.cursor/commands/fix-review.md). Copyright stays with the author.

Fix Review Command

Name: fix-review
Author: grimm00

Review old deferred issues to identify candidates for addressing. Helps prioritize which old issues are worth fixing now.

Workflow Overview

When to use:

After several phases/PRs completed
When looking for quick wins or accumulated issues
Before starting new feature work
To clean up technical debt

Key principle: Review deferred issues periodically to identify opportunities for improvement and technical debt reduction.

Usage

Command: @fix-review [options]

Examples:

@fix-review - Review all old deferred issues
@fix-review --priority MEDIUM - Review only MEDIUM priority issues
@fix-review --min-age 30 - Review issues older than 30 days
@fix-review --accumulated - Find issues that have accumulated (similar issues)
@fix-review --quick-wins - Find LOW effort issues (quick wins)

Options:

--priority LEVEL - Filter by priority (CRITICAL, HIGH, MEDIUM, LOW)
--min-effort LEVEL - Filter by minimum effort (LOW, MEDIUM, HIGH)
--min-age DAYS - Only review issues older than N days
--accumulated - Find issues that appear multiple times (similar issues)
--quick-wins - Find LOW effort issues that can be fixed quickly
--by-pr - Group issues by PR number
--by-file - Group issues by affected file

Step-by-Step Process

1. Scan All Deferred Issues

Sources:

Fix tracking document: docs/maintainers/planning/features/projects/fix/README.md (main hub)
PR hub files: docs/maintainers/planning/features/projects/fix/pr##/README.md
Sourcery review files: docs/maintainers/feedback/sourcery/pr##.md
Individual fix plans: docs/maintainers/planning/features/projects/fix/pr##/batch-*.md or pr##/issue-*.md
Archived fixes: docs/maintainers/planning/features/projects/fix/archived/pr##/

Extract:

Issue ID (PR##-#N)
Priority, Impact, Effort
Description
File location
Age (days since PR merged)
Status (deferred, not fixed, etc.)

Checklist:

All deferred issues identified
Age calculated for each issue
Status verified (not already fixed)

2. Filter and Group Issues

Apply filters:

Priority filter (if specified)
Effort filter (if specified)
Age filter (if specified)
Accumulation filter (if specified)

Group by:

By PR: All issues from same PR together
By File: Issues affecting same file together
By Type: Similar issues (e.g., all test improvements)
By Priority: Highest priority first

Checklist:

Filters applied
Issues grouped logically
Duplicates identified

3. Identify Candidates

Criteria for addressing:

Accumulated Issues
- Same issue appears multiple times
- Similar issues that can be batched
- Example: Multiple "use click.Choice" suggestions
Quick Wins
- LOW effort, LOW priority
- Can be fixed quickly
- Example: Style improvements, minor refactors
Blocking Issues
- Fixing enables other improvements
- Reduces technical debt
- Example: Code duplication that blocks refactoring
Old Issues
- Been deferred for a while
- Code may have changed making fix easier
- Example: Issues from early PRs
Related to Current Work
- Fixing while working on related code
- Reduces context switching
- Example: CLI improvements while adding CLI features

Checklist:

4. Generate Review Report

Report Format:

# Fix Review Report

**Date:** YYYY-MM-DD  
**Total Deferred Issues:** [N]  
**Candidates for Addressing:** [M]

---

## Summary

- **Accumulated Issues:** [X] (can batch together)
- **Quick Wins:** [Y] (LOW effort, can fix quickly)
- **Blocking Issues:** [Z] (enable other improvements)
- **Old Issues:** [W] (deferred for [N] days)

---

## Accumulated Issues

### Issue Type: [Description]

**Occurrences:** [N] times  
**PRs:** #[N1], #[N2], #[N3]  
**Total Effort:** [Effort Level]

**Issues:**
- PR##-#N: [Description] ([Priority], [Effort])
- PR##-#M: [Description] ([Priority], [Effort])
- PR##-#K: [Description] ([Priority], [Effort])

**Recommendation:** Batch together in single fix plan

---

## Quick Wins

| Issue | Priority | Effort | Age | Description |
|-------|----------|--------|-----|-------------|
| PR##-#N | 🟢 LOW | 🟢 LOW | [N] days | [Description] |

**Recommendation:** Create quick-wins batch

---

## Blocking Issues

| Issue | Priority | Effort | Blocks | Description |
|-------|----------|--------|--------|-------------|
| PR##-#N | 🟡 MEDIUM | 🟡 MEDIUM | [What it blocks] | [Description] |

**Recommendation:** Address before [blocked work]

---

## Old Issues (30+ days)

| Issue | Priority | Effort | Age | Description |
|-------|----------|--------|-----|-------------|
| PR##-#N | 🟡 MEDIUM | 🟢 LOW | [N] days | [Description] |

**Recommendation:** Review if still relevant

---

## Recommendations

1. **Immediate:** [Top recommendation]
2. **Next:** [Second recommendation]
3. **Future:** [Long-term recommendation]

Checklist:

Report generated
Candidates identified
Recommendations provided
Report saved for reference

5. Create Fix Plans (Optional)

If issues are worth addressing:

Use /fix-plan --from-review-report command:

# Create batches from latest review report
/fix-plan --from-review-report fix-review-report-2025-12-05.md

# Create specific batch from report
/fix-plan --from-review-report fix-review-report-2025-12-05.md --batch "Quick Wins"

# Create only Quick Wins batch
/fix-plan --from-review-report --quick-wins

The command will:
- Parse review report recommendations
- Resolve issue details from source PRs
- Create cross-PR batches
- Update fix tracking
Or manually create batches:
- Group accumulated issues
- Create quick-wins batch
- Address blocking issues first

Checklist:

Review report saved
Fix plans created using /fix-plan --from-review-report (if addressing)
Fix tracking updated
Issues marked as planned

Common Scenarios

Scenario 1: Accumulated Similar Issues

Situation: Multiple PRs have similar issues (e.g., "use click.Choice")

Action:

Identify all occurrences
Create single batch for all
Fix once, addresses multiple PRs

Example:

PR #10: Use click.Choice for status
PR #12: Use click.Choice for status
PR #15: Use click.Choice for classification → Batch together: "CLI validation improvements"

Scenario 2: Quick Wins

Situation: Many LOW effort, LOW priority issues accumulated

Action:

Create quick-wins batch
Fix all in single PR
Clean up technical debt

Example:

5 LOW/LOW issues from different PRs → Batch: "Code quality quick wins"

Scenario 3: Blocking Refactoring

Situation: Code duplication issue blocking other improvements

Action:

Prioritize fixing duplication
Enables cleaner refactoring
Reduces future technical debt

Example:

PR #8 Overall: Code duplication → Fix before major refactoring work

Tips

When to Review

After each phase: Quick review of new deferred issues
Monthly: Comprehensive review of all deferred issues
Before major refactoring: Check for blocking issues
When looking for work: Find quick wins or accumulated issues

What to Look For

Patterns: Similar issues across PRs
Accumulation: Many small issues that can batch
Dependencies: Issues that block other work
Age: Old issues that may be easier now

Prioritization

Blocking issues (enable other work)
Accumulated issues (fix once, helps many)
Quick wins (easy, builds momentum)
Old issues (if still relevant)

Reference

Fix Tracking:

docs/maintainers/planning/features/projects/fix/README.md (main hub)
docs/maintainers/planning/features/projects/fix/pr##/README.md (PR hubs)
docs/maintainers/planning/features/projects/fix/archived/README.md (archive hub)

Sourcery Reviews:

docs/maintainers/feedback/sourcery/pr##.md

Related Commands:

/fix-plan - Create fix plans from review
/fix-implement - Implement fix batches

Last Updated: 2025-12-04
Status: ✅ Active
Next: Run periodically to identify fix opportunities

# Fix Review Command Review old deferred issues to identify candidates for addressing. Helps prioritize which old issues are worth fixing now. --- ## Workflow Overview **When to use:** - After several phases/PRs completed - When looking for quick wins or accumulated issues - Before starting new feature work - To clean up technical debt **Key principle:** Review deferred issues periodically to identify opportunities for improvement and technical debt reduction. --- ## Usage **Command:** `@fix-review [options]` **Examples:** - `@fix-review` - Review all old deferred issues - `@fix-review --priority MEDIUM` - Review only MEDIUM priority issues - `@fix-review --min-age 30` - Review issues older than 30 days - `@fix-review --accumulated` - Find issues that have accumulated (similar issues) - `@fix-review --quick-wins` - Find LOW effort issues (quick wins) **Options:** - `--priority LEVEL` - Filter by priority (CRITICAL, HIGH, MEDIUM, LOW) - `--min-effort LEVEL` - Filter by minimum effort (LOW, MEDIUM, HIGH) - `--min-age DAYS` - Only review issues older than N days - `--accumulated` - Find issues that appear multiple times (similar issues) - `--quick-wins` - Find LOW effort issues that can be fixed quickly - `--by-pr` - Group issues by PR number - `--by-file` - Group issues by affected file --- ## Step-by-Step Process ### 1. Scan All Deferred Issues **Sources:** - Fix tracking document: `docs/maintainers/planning/features/projects/fix/README.md` (main hub) - PR hub files: `docs/maintainers/planning/features/projects/fix/pr##/README.md` - Sourcery review files: `docs/maintainers/feedback/sourcery/pr##.md` - Individual fix plans: `docs/maintainers/planning/features/projects/fix/pr##/batch-*.md` or `pr##/issue-*.md` - Archived fixes: `docs/maintainers/planning/features/projects/fix/archived/pr##/` **Extract:** - Issue ID (PR##-#N) - Priority, Impact, Effort - Description - File location - Age (days since PR merged) - Status (deferred, not fixed, etc.) **Checklist:** - [ ] All deferred issues identified - [ ] Age calculated for each issue - [ ] Status verified (not already fixed) --- ### 2. Filter and Group Issues **Apply filters:** - Priority filter (if specified) - Effort filter (if specified) - Age filter (if specified) - Accumulation filter (if specified) **Group by:** - **By PR:** All issues from same PR together - **By File:** Issues affecting same file together - **By Type:** Similar issues (e.g., all test improvements) - **By Priority:** Highest priority first **Checklist:** - [ ] Filters applied - [ ] Issues grouped logically - [ ] Duplicates identified --- ### 3. Identify Candidates **Criteria for addressing:** 1. **Accumulated Issues** - Same issue appears multiple times - Similar issues that can be batched - Example: Multiple "use click.Choice" suggestions 2. **Quick Wins** - LOW effort, LOW priority - Can be fixed quickly - Example: Style improvements, minor refactors 3. **Blocking Issues** - Fixing enables other improvements - Reduces technical debt - Example: Code duplication that blocks refactoring 4. **Old Issues** - Been deferred for a while - Code may have changed making fix easier - Example: Issues from early PRs 5. **Related to Current Work** - Fixing while working on related code - Reduces context switching - Example: CLI improvements while adding CLI features **Checklist:** - [ ] Accumulated issues identified - [ ] Quick wins identified - [ ] Blocking issues identified - [ ] Old issues reviewed - [ ] Related issues noted --- ### 4. Generate Review Report **Report Format:** ```markdown # Fix Review Report **Date:** YYYY-MM-DD **Total Deferred Issues:** [N] **Candidates for Addressing:** [M] --- ## Summary - **Accumulated Issues:** [X] (can batch together) - **Quick Wins:** [Y] (LOW effort, can fix quickly) - **Blocking Issues:** [Z] (enable other improvements) - **Old Issues:** [W] (deferred for [N] days) --- ## Accumulated Issues ### Issue Type: [Description] **Occurrences:** [N] times **PRs:** #[N1], #[N2], #[N3] **Total Effort:** [Effort Level] **Issues:** - PR##-#N: [Description] ([Priority], [Effort]) - PR##-#M: [Description] ([Priority], [Effort]) - PR##-#K: [Description] ([Priority], [Effort]) **Recommendation:** Batch together in single fix plan --- ## Quick Wins | Issue | Priority | Effort | Age | Description | |-------|----------|--------|-----|-------------| | PR##-#N | 🟢 LOW | 🟢 LOW | [N] days | [Description] | **Recommendation:** Create quick-wins batch --- ## Blocking Issues | Issue | Priority | Effort | Blocks | Description | |-------|----------|--------|--------|-------------| | PR##-#N | 🟡 MEDIUM | 🟡 MEDIUM | [What it blocks] | [Description] | **Recommendation:** Address before [blocked work] --- ## Old Issues (30+ days) | Issue | Priority | Effort | Age | Description | |-------|----------|--------|-----|-------------| | PR##-#N | 🟡 MEDIUM | 🟢 LOW | [N] days | [Description] | **Recommendation:** Review if still relevant --- ## Recommendations 1. **Immediate:** [Top recommendation] 2. **Next:** [Second recommendation] 3. **Future:** [Long-term recommendation] ``` **Checklist:** - [ ] Report generated - [ ] Candidates identified - [ ] Recommendations provided - [ ] Report saved for reference --- ### 5. Create Fix Plans (Optional) **If issues are worth addressing:** 1. **Use `/fix-plan --from-review-report` command:** ```bash # Create batches from latest review report /fix-plan --from-review-report fix-review-report-2025-12-05.md # Create specific batch from report /fix-plan --from-review-report fix-review-report-2025-12-05.md --batch "Quick Wins" # Create only Quick Wins batch /fix-plan --from-review-report --quick-wins ``` 2. **The command will:** - Parse review report recommendations - Resolve issue details from source PRs - Create cross-PR batches - Update fix tracking 3. **Or manually create batches:** - Group accumulated issues - Create quick-wins batch - Address blocking issues first **Checklist:** - [ ] Review report saved - [ ] Fix plans created using `/fix-plan --from-review-report` (if addressing) - [ ] Fix tracking updated - [ ] Issues marked as planned --- ## Common Scenarios ### Scenario 1: Accumulated Similar Issues **Situation:** Multiple PRs have similar issues (e.g., "use click.Choice") **Action:** - Identify all occurrences - Create single batch for all - Fix once, addresses multiple PRs **Example:** - PR #10: Use click.Choice for status - PR #12: Use click.Choice for status - PR #15: Use click.Choice for classification → Batch together: "CLI validation improvements" --- ### Scenario 2: Quick Wins **Situation:** Many LOW effort, LOW priority issues accumulated **Action:** - Create quick-wins batch - Fix all in single PR - Clean up technical debt **Example:** - 5 LOW/LOW issues from different PRs → Batch: "Code quality quick wins" --- ### Scenario 3: Blocking Refactoring **Situation:** Code duplication issue blocking other improvements **Action:** - Prioritize fixing duplication - Enables cleaner refactoring - Reduces future technical debt **Example:** - PR #8 Overall: Code duplication → Fix before major refactoring work --- ## Tips ### When to Review - **After each phase:** Quick review of new deferred issues - **Monthly:** Comprehensive review of all deferred issues - **Before major refactoring:** Check for blocking issues - **When looking for work:** Find quick wins or accumulated issues ### What to Look For - **Patterns:** Similar issues across PRs - **Accumulation:** Many small issues that can batch - **Dependencies:** Issues that block other work - **Age:** Old issues that may be easier now ### Prioritization 1. **Blocking issues** (enable other work) 2. **Accumulated issues** (fix once, helps many) 3. **Quick wins** (easy, builds momentum) 4. **Old issues** (if still relevant) --- ## Reference **Fix Tracking:** - `docs/maintainers/planning/features/projects/fix/README.md` (main hub) - `docs/maintainers/planning/features/projects/fix/pr##/README.md` (PR hubs) - `docs/maintainers/planning/features/projects/fix/archived/README.md` (archive hub) **Sourcery Reviews:** - `docs/maintainers/feedback/sourcery/pr##.md` **Related Commands:** - `/fix-plan` - Create fix plans from review - `/fix-implement` - Implement fix batches --- **Last Updated:** 2025-12-04 **Status:** ✅ Active **Next:** Run periodically to identify fix opportunities

{ "prompt": "# Fix Review Command\n\nReview old deferred issues to identify candidates for addressing. Helps prioritize which old issues are worth fixing now.\n\n---\n\n## Workflow Overview\n\n**When to use:**\n- After several phases/PRs completed\n- When looking for quick wins or accumulated issues\n- Before starting new feature work\n- To clean up technical debt\n\n**Key principle:** Review deferred issues periodically to identify opportunities for improvement and technical debt reduction.\n\n---\n\n## Usage\n\n**Command:** `@fix-review [options]`\n\n**Examples:**\n- `@fix-review` - Review all old deferred issues\n- `@fix-review --priority MEDIUM` - Review only MEDIUM priority issues\n- `@fix-review --min-age 30` - Review issues older than 30 days\n- `@fix-review --accumulated` - Find issues that have accumulated (similar issues)\n- `@fix-review --quick-wins` - Find LOW effort issues (quick wins)\n\n**Options:**\n- `--priority LEVEL` - Filter by priority (CRITICAL, HIGH, MEDIUM, LOW)\n- `--min-effort LEVEL` - Filter by minimum effort (LOW, MEDIUM, HIGH)\n- `--min-age DAYS` - Only review issues older than N days\n- `--accumulated` - Find issues that appear multiple times (similar issues)\n- `--quick-wins` - Find LOW effort issues that can be fixed quickly\n- `--by-pr` - Group issues by PR number\n- `--by-file` - Group issues by affected file\n\n---\n\n## Step-by-Step Process\n\n### 1. Scan All Deferred Issues\n\n**Sources:**\n- Fix tracking document: `docs/maintainers/planning/features/projects/fix/README.md` (main hub)\n- PR hub files: `docs/maintainers/planning/features/projects/fix/pr##/README.md`\n- Sourcery review files: `docs/maintainers/feedback/sourcery/pr##.md`\n- Individual fix plans: `docs/maintainers/planning/features/projects/fix/pr##/batch-*.md` or `pr##/issue-*.md`\n- Archived fixes: `docs/maintainers/planning/features/projects/fix/archived/pr##/`\n\n**Extract:**\n- Issue ID (PR##-#N)\n- Priority, Impact, Effort\n- Description\n- File location\n- Age (days since PR merged)\n- Status (deferred, not fixed, etc.)\n\n**Checklist:**\n- [ ] All deferred issues identified\n- [ ] Age calculated for each issue\n- [ ] Status verified (not already fixed)\n\n---\n\n### 2. Filter and Group Issues\n\n**Apply filters:**\n- Priority filter (if specified)\n- Effort filter (if specified)\n- Age filter (if specified)\n- Accumulation filter (if specified)\n\n**Group by:**\n- **By PR:** All issues from same PR together\n- **By File:** Issues affecting same file together\n- **By Type:** Similar issues (e.g., all test improvements)\n- **By Priority:** Highest priority first\n\n**Checklist:**\n- [ ] Filters applied\n- [ ] Issues grouped logically\n- [ ] Duplicates identified\n\n---\n\n### 3. Identify Candidates\n\n**Criteria for addressing:**\n\n1. **Accumulated Issues**\n - Same issue appears multiple times\n - Similar issues that can be batched\n - Example: Multiple \"use click.Choice\" suggestions\n\n2. **Quick Wins**\n - LOW effort, LOW priority\n - Can be fixed quickly\n - Example: Style improvements, minor refactors\n\n3. **Blocking Issues**\n - Fixing enables other improvements\n - Reduces technical debt\n - Example: Code duplication that blocks refactoring\n\n4. **Old Issues**\n - Been deferred for a while\n - Code may have changed making fix easier\n - Example: Issues from early PRs\n\n5. **Related to Current Work**\n - Fixing while working on related code\n - Reduces context switching\n - Example: CLI improvements while adding CLI features\n\n**Checklist:**\n- [ ] Accumulated issues identified\n- [ ] Quick wins identified\n- [ ] Blocking issues identified\n- [ ] Old issues reviewed\n- [ ] Related issues noted\n\n---\n\n### 4. Generate Review Report\n\n**Report Format:**\n\n```markdown\n# Fix Review Report\n\n**Date:** YYYY-MM-DD \n**Total Deferred Issues:** [N] \n**Candidates for Addressing:** [M]\n\n---\n\n## Summary\n\n- **Accumulated Issues:** [X] (can batch together)\n- **Quick Wins:** [Y] (LOW effort, can fix quickly)\n- **Blocking Issues:** [Z] (enable other improvements)\n- **Old Issues:** [W] (deferred for [N] days)\n\n---\n\n## Accumulated Issues\n\n### Issue Type: [Description]\n\n**Occurrences:** [N] times \n**PRs:** #[N1], #[N2], #[N3] \n**Total Effort:** [Effort Level]\n\n**Issues:**\n- PR##-#N: [Description] ([Priority], [Effort])\n- PR##-#M: [Description] ([Priority], [Effort])\n- PR##-#K: [Description] ([Priority], [Effort])\n\n**Recommendation:** Batch together in single fix plan\n\n---\n\n## Quick Wins\n\n| Issue | Priority | Effort | Age | Description |\n|-------|----------|--------|-----|-------------|\n| PR##-#N | 🟢 LOW | 🟢 LOW | [N] days | [Description] |\n\n**Recommendation:** Create quick-wins batch\n\n---\n\n## Blocking Issues\n\n| Issue | Priority | Effort | Blocks | Description |\n|-------|----------|--------|--------|-------------|\n| PR##-#N | 🟡 MEDIUM | 🟡 MEDIUM | [What it blocks] | [Description] |\n\n**Recommendation:** Address before [blocked work]\n\n---\n\n## Old Issues (30+ days)\n\n| Issue | Priority | Effort | Age | Description |\n|-------|----------|--------|-----|-------------|\n| PR##-#N | 🟡 MEDIUM | 🟢 LOW | [N] days | [Description] |\n\n**Recommendation:** Review if still relevant\n\n---\n\n## Recommendations\n\n1. **Immediate:** [Top recommendation]\n2. **Next:** [Second recommendation]\n3. **Future:** [Long-term recommendation]\n```\n\n**Checklist:**\n- [ ] Report generated\n- [ ] Candidates identified\n- [ ] Recommendations provided\n- [ ] Report saved for reference\n\n---\n\n### 5. Create Fix Plans (Optional)\n\n**If issues are worth addressing:**\n\n1. **Use `/fix-plan --from-review-report` command:**\n ```bash\n # Create batches from latest review report\n /fix-plan --from-review-report fix-review-report-2025-12-05.md\n \n # Create specific batch from report\n /fix-plan --from-review-report fix-review-report-2025-12-05.md --batch \"Quick Wins\"\n \n # Create only Quick Wins batch\n /fix-plan --from-review-report --quick-wins\n ```\n\n2. **The command will:**\n - Parse review report recommendations\n - Resolve issue details from source PRs\n - Create cross-PR batches\n - Update fix tracking\n\n3. **Or manually create batches:**\n - Group accumulated issues\n - Create quick-wins batch\n - Address blocking issues first\n\n**Checklist:**\n- [ ] Review report saved\n- [ ] Fix plans created using `/fix-plan --from-review-report` (if addressing)\n- [ ] Fix tracking updated\n- [ ] Issues marked as planned\n\n---\n\n## Common Scenarios\n\n### Scenario 1: Accumulated Similar Issues\n\n**Situation:** Multiple PRs have similar issues (e.g., \"use click.Choice\")\n\n**Action:**\n- Identify all occurrences\n- Create single batch for all\n- Fix once, addresses multiple PRs\n\n**Example:**\n- PR #10: Use click.Choice for status\n- PR #12: Use click.Choice for status\n- PR #15: Use click.Choice for classification\n→ Batch together: \"CLI validation improvements\"\n\n---\n\n### Scenario 2: Quick Wins\n\n**Situation:** Many LOW effort, LOW priority issues accumulated\n\n**Action:**\n- Create quick-wins batch\n- Fix all in single PR\n- Clean up technical debt\n\n**Example:**\n- 5 LOW/LOW issues from different PRs\n→ Batch: \"Code quality quick wins\"\n\n---\n\n### Scenario 3: Blocking Refactoring\n\n**Situation:** Code duplication issue blocking other improvements\n\n**Action:**\n- Prioritize fixing duplication\n- Enables cleaner refactoring\n- Reduces future technical debt\n\n**Example:**\n- PR #8 Overall: Code duplication\n→ Fix before major refactoring work\n\n---\n\n## Tips\n\n### When to Review\n\n- **After each phase:** Quick review of new deferred issues\n- **Monthly:** Comprehensive review of all deferred issues\n- **Before major refactoring:** Check for blocking issues\n- **When looking for work:** Find quick wins or accumulated issues\n\n### What to Look For\n\n- **Patterns:** Similar issues across PRs\n- **Accumulation:** Many small issues that can batch\n- **Dependencies:** Issues that block other work\n- **Age:** Old issues that may be easier now\n\n### Prioritization\n\n1. **Blocking issues** (enable other work)\n2. **Accumulated issues** (fix once, helps many)\n3. **Quick wins** (easy, builds momentum)\n4. **Old issues** (if still relevant)\n\n---\n\n## Reference\n\n**Fix Tracking:**\n- `docs/maintainers/planning/features/projects/fix/README.md` (main hub)\n- `docs/maintainers/planning/features/projects/fix/pr##/README.md` (PR hubs)\n- `docs/maintainers/planning/features/projects/fix/archived/README.md` (archive hub)\n\n**Sourcery Reviews:**\n- `docs/maintainers/feedback/sourcery/pr##.md`\n\n**Related Commands:**\n- `/fix-plan` - Create fix plans from review\n- `/fix-implement` - Implement fix batches\n\n---\n\n**Last Updated:** 2025-12-04 \n**Status:** ✅ Active \n**Next:** Run periodically to identify fix opportunities", "variables": [], "notes": "Review old deferred issues to identify candidates for addressing. Helps prioritize which old issues are worth fixing now.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/grimm00/work-prod", "path": ".cursor/commands/fix-review.md", "ref": "6c135a90c410fcc2896cfbc3d1c965435a2c87b6", "url": "https://github.com/grimm00/work-prod/blob/6c135a90c410fcc2896cfbc3d1c965435a2c87b6/.cursor/commands/fix-review.md", "key": "grimm00/work-prod/.cursor/commands/fix-review.md" } } }

fix-review

About

Fix Review Command

Workflow Overview

Usage

Step-by-Step Process

1. Scan All Deferred Issues

2. Filter and Group Issues

3. Identify Candidates

4. Generate Review Report

5. Create Fix Plans (Optional)

Common Scenarios

Scenario 1: Accumulated Similar Issues

Scenario 2: Quick Wins

Scenario 3: Blocking Refactoring

Tips

When to Review

What to Look For

Prioritization

Reference

Use it

Manifest

Reviews