Prompt file imported from twalmsley/poly-cover (.cursor/commands/plan-issue-fix.md). Copyright stays with the author.

Plan Issue Fix

Name: plan-issue-fix
Author: twalmsley

This command fetches a GitHub issue, creates a detailed plan for fixing it, and posts the plan as a comment on the issue.

Usage

The user should provide an issue number (e.g., "plan fix for issue #42" or "plan issue 42").

Steps

Get the issue number from the user's request - Extract the issue number from their message. If not provided, ask for it.
Fetch issue details using gh issue view <number> --json title,body,number,state,labels,author,createdAt,updatedAt to get comprehensive issue information.
Analyze the issue:
- Read the issue title and body to understand what needs to be fixed
- Check the codebase to understand the relevant code areas
- Identify the root cause and affected components
- Consider edge cases and testing requirements
Create a detailed fix plan that includes:
- Problem Summary: Brief description of what needs to be fixed
- Root Cause Analysis: Why the issue exists
- Proposed Solution: Step-by-step approach to fix the issue
- Affected Components: Files, classes, and modules that need changes
- Testing Strategy: What tests need to be added or updated
- Implementation Steps: Detailed breakdown of the work required
- Risk Assessment: Potential side effects or breaking changes
Format the plan as a markdown comment with clear sections and code blocks where appropriate.
Post the plan as a comment on the issue using:
```
gh issue comment <number> --body-file <temp-file>
```
Or use --body with the formatted plan text.
Confirm completion - Let the user know the plan has been posted to the issue.

Example Output Format

The plan comment should follow this structure:

## Fix Plan for Issue #<number>

### Problem Summary
[Brief description]

### Root Cause Analysis
[Why this issue exists]

### Proposed Solution
[High-level approach]

### Affected Components
- File: `path/to/file.java`
- Class: `ClassName`
- [Other components]

### Testing Strategy
- [ ] Unit tests for [component]
- [ ] Integration tests for [scenario]
- [ ] Edge case: [description]

### Implementation Steps
1. [Step 1]
2. [Step 2]
3. [Step 3]

### Risk Assessment
- [Potential risks and mitigations]

# Plan Issue Fix This command fetches a GitHub issue, creates a detailed plan for fixing it, and posts the plan as a comment on the issue. ## Usage The user should provide an issue number (e.g., "plan fix for issue #42" or "plan issue 42"). ## Steps 1. **Get the issue number from the user's request** - Extract the issue number from their message. If not provided, ask for it. 2. **Fetch issue details** using `gh issue view <number> --json title,body,number,state,labels,author,createdAt,updatedAt` to get comprehensive issue information. 3. **Analyze the issue**: - Read the issue title and body to understand what needs to be fixed - Check the codebase to understand the relevant code areas - Identify the root cause and affected components - Consider edge cases and testing requirements 4. **Create a detailed fix plan** that includes: - **Problem Summary**: Brief description of what needs to be fixed - **Root Cause Analysis**: Why the issue exists - **Proposed Solution**: Step-by-step approach to fix the issue - **Affected Components**: Files, classes, and modules that need changes - **Testing Strategy**: What tests need to be added or updated - **Implementation Steps**: Detailed breakdown of the work required - **Risk Assessment**: Potential side effects or breaking changes 5. **Format the plan as a markdown comment** with clear sections and code blocks where appropriate. 6. **Post the plan as a comment** on the issue using: ``` gh issue comment <number> --body-file <temp-file> ``` Or use `--body` with the formatted plan text. 7. **Confirm completion** - Let the user know the plan has been posted to the issue. ## Example Output Format The plan comment should follow this structure: ```markdown ## Fix Plan for Issue #<number> ### Problem Summary [Brief description] ### Root Cause Analysis [Why this issue exists] ### Proposed Solution [High-level approach] ### Affected Components - File: `path/to/file.java` - Class: `ClassName` - [Other components] ### Testing Strategy - [ ] Unit tests for [component] - [ ] Integration tests for [scenario] - [ ] Edge case: [description] ### Implementation Steps 1. [Step 1] 2. [Step 2] 3. [Step 3] ### Risk Assessment - [Potential risks and mitigations] ```

{ "prompt": "# Plan Issue Fix\n\nThis command fetches a GitHub issue, creates a detailed plan for fixing it, and posts the plan as a comment on the issue.\n\n## Usage\nThe user should provide an issue number (e.g., \"plan fix for issue #42\" or \"plan issue 42\").\n\n## Steps\n\n1. **Get the issue number from the user's request** - Extract the issue number from their message. If not provided, ask for it.\n\n2. **Fetch issue details** using `gh issue view <number> --json title,body,number,state,labels,author,createdAt,updatedAt` to get comprehensive issue information.\n\n3. **Analyze the issue**:\n - Read the issue title and body to understand what needs to be fixed\n - Check the codebase to understand the relevant code areas\n - Identify the root cause and affected components\n - Consider edge cases and testing requirements\n\n4. **Create a detailed fix plan** that includes:\n - **Problem Summary**: Brief description of what needs to be fixed\n - **Root Cause Analysis**: Why the issue exists\n - **Proposed Solution**: Step-by-step approach to fix the issue\n - **Affected Components**: Files, classes, and modules that need changes\n - **Testing Strategy**: What tests need to be added or updated\n - **Implementation Steps**: Detailed breakdown of the work required\n - **Risk Assessment**: Potential side effects or breaking changes\n\n5. **Format the plan as a markdown comment** with clear sections and code blocks where appropriate.\n\n6. **Post the plan as a comment** on the issue using:\n ```\n gh issue comment <number> --body-file <temp-file>\n ```\n Or use `--body` with the formatted plan text.\n\n7. **Confirm completion** - Let the user know the plan has been posted to the issue.\n\n## Example Output Format\n\nThe plan comment should follow this structure:\n\n```markdown\n## Fix Plan for Issue #<number>\n\n### Problem Summary\n[Brief description]\n\n### Root Cause Analysis\n[Why this issue exists]\n\n### Proposed Solution\n[High-level approach]\n\n### Affected Components\n- File: `path/to/file.java`\n- Class: `ClassName`\n- [Other components]\n\n### Testing Strategy\n- [ ] Unit tests for [component]\n- [ ] Integration tests for [scenario]\n- [ ] Edge case: [description]\n\n### Implementation Steps\n1. [Step 1]\n2. [Step 2]\n3. [Step 3]\n\n### Risk Assessment\n- [Potential risks and mitigations]\n```", "variables": [], "notes": "This command fetches a GitHub issue, creates a detailed plan for fixing it, and posts the plan as a comment on the issue.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/twalmsley/poly-cover", "path": ".cursor/commands/plan-issue-fix.md", "ref": "711756b899043402f93f49aec1147ede27c556bb", "url": "https://github.com/twalmsley/poly-cover/blob/711756b899043402f93f49aec1147ede27c556bb/.cursor/commands/plan-issue-fix.md", "key": "twalmsley/poly-cover/.cursor/commands/plan-issue-fix.md" } } }

plan-issue-fix

About

Plan Issue Fix

Usage

Steps

Example Output Format

Use it

Manifest

Reviews