Name: fix-pr
Author: wghglory

Prompt file imported from wghglory/ngx-lift-workspace (.cursor/commands/fix-pr.md). Copyright stays with the author.

Fix PR Review Comments - Plan Mode

Generates a fix plan for actionable code review comments from a GitHub PR. The author can review the plan and decide whether to implement the fixes.

Input

Branch name: [BRANCH_NAME]

Steps

Validate Branch
- Check current branch matches [BRANCH_NAME]
- If mismatch, STOP with checkout instructions
Fetch PR Data
- Search for PR: repo:vcf/dsm-ui head:[BRANCH_NAME] is:pr
- Extract PR number
- Fetch review comments and summaries
- If no PR/reviews found, STOP with clear message
Analyze Comments
- Categorize as Actionable (clear fix) or Skipped (questions, unclear, approvals)
- Create organized list of actionable items with file paths and line numbers
Generate Fix Plan
- For each actionable item:
  - Read affected file (if needed for context)
  - Analyze the issue and review comment
  - Propose specific fix following .cursor/rules/ standards
  - Identify potential impact and risks
  - Estimate complexity (simple/moderate/complex)
- Group fixes by file for better organization
Present Fix Plan
- Display comprehensive plan with:
  - PR Information: PR number, title, branch
  - Summary: Total actionable items, skipped items
  - Fix Plan by File:
    - File path
    - Line number(s)
    - Review comment
    - Proposed fix description
    - Code snippet (before/after if applicable)
    - Complexity estimate
    - Potential risks/considerations
  - Skipped Comments: List with reasons
  - Next Steps: Instructions for author
Author Decision
- Author reviews the plan
- Author can:
  - Accept all fixes (implement manually or ask AI to implement specific ones)
  - Accept some fixes (cherry-pick which to implement)
  - Reject and handle manually
  - Ask for clarification on specific fixes

Output Format

# Fix Plan for PR #[NUMBER]: [PR_TITLE]

**Branch**: [BRANCH_NAME] **Total Actionable Items**: [COUNT] **Skipped Items**: [COUNT]

---

## Actionable Fixes

### 📁 [file1.ts]

#### Fix 1: [Brief description]

- **Line(s)**: [LINE_NUMBER]
- **Complexity**: [Simple/Moderate/Complex]
- **Review Comment**:
  > [Original review comment]
- **Proposed Fix**: [Detailed description of what needs to be changed and why]
- **Code Change**:

  ```typescript
  // Before:
  [current code]

  // After:
  [proposed code]
  ```

Considerations: [Any risks, dependencies, or things to watch out for]

📁 [file2.ts]

[Similar structure for each file]

Skipped Comments

[file.ts:LINE] - [Reason for skipping]

[Comment text]

Next Steps

Review the fix plan above
For fixes you want to implement:
- Implement manually, or
- Ask: "Implement fix [number] from the plan"
Run linting: npx nx lint [affected-projects]
Test your changes
Commit with appropriate message
Push when ready

Note: No changes have been made to your code. This is a plan only.


## Notes

- **No automatic fixes** - generates plan only
- **No commits** - author decides when to commit
- **No code changes** - read-only analysis
- Only analyze clear, actionable comments
- Follow all project standards from `.cursor/rules/`
- Author maintains full control over implementation

Install fix-pr and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# Fix PR Review Comments - Plan Mode Generates a fix plan for actionable code review comments from a GitHub PR. The author can review the plan and decide whether to implement the fixes. ## Input Branch name: `[BRANCH_NAME]` ## Steps 1. **Validate Branch** - Check current branch matches `[BRANCH_NAME]` - If mismatch, STOP with checkout instructions 2. **Fetch PR Data** - Search for PR: `repo:vcf/dsm-ui head:[BRANCH_NAME] is:pr` - Extract PR number - Fetch review comments and summaries - If no PR/reviews found, STOP with clear message 3. **Analyze Comments** - Categorize as **Actionable** (clear fix) or **Skipped** (questions, unclear, approvals) - Create organized list of actionable items with file paths and line numbers 4. **Generate Fix Plan** - For each actionable item: - Read affected file (if needed for context) - Analyze the issue and review comment - Propose specific fix following `.cursor/rules/` standards - Identify potential impact and risks - Estimate complexity (simple/moderate/complex) - Group fixes by file for better organization 5. **Present Fix Plan** - Display comprehensive plan with: - **PR Information**: PR number, title, branch - **Summary**: Total actionable items, skipped items - **Fix Plan by File**: - File path - Line number(s) - Review comment - Proposed fix description - Code snippet (before/after if applicable) - Complexity estimate - Potential risks/considerations - **Skipped Comments**: List with reasons - **Next Steps**: Instructions for author 6. **Author Decision** - Author reviews the plan - Author can: - Accept all fixes (implement manually or ask AI to implement specific ones) - Accept some fixes (cherry-pick which to implement) - Reject and handle manually - Ask for clarification on specific fixes ## Output Format ````markdown # Fix Plan for PR #[NUMBER]: [PR_TITLE] **Branch**: [BRANCH_NAME] **Total Actionable Items**: [COUNT] **Skipped Items**: [COUNT] --- ## Actionable Fixes ### 📁 [file1.ts] #### Fix 1: [Brief description] - **Line(s)**: [LINE_NUMBER] - **Complexity**: [Simple/Moderate/Complex] - **Review Comment**: > [Original review comment] - **Proposed Fix**: [Detailed description of what needs to be changed and why] - **Code Change**: ```typescript // Before: [current code] // After: [proposed code] ``` ```` - **Considerations**: [Any risks, dependencies, or things to watch out for] --- ### 📁 [file2.ts] [Similar structure for each file] --- ## Skipped Comments 1. **[file.ts:LINE]** - [Reason for skipping] > [Comment text] --- ## Next Steps 1. Review the fix plan above 2. For fixes you want to implement: - Implement manually, or - Ask: "Implement fix [number] from the plan" 3. Run linting: `npx nx lint [affected-projects]` 4. Test your changes 5. Commit with appropriate message 6. Push when ready **Note**: No changes have been made to your code. This is a plan only. ``` ## Notes - **No automatic fixes** - generates plan only - **No commits** - author decides when to commit - **No code changes** - read-only analysis - Only analyze clear, actionable comments - Follow all project standards from `.cursor/rules/` - Author maintains full control over implementation ```

{ "prompt": "# Fix PR Review Comments - Plan Mode\n\nGenerates a fix plan for actionable code review comments from a GitHub PR. The author can review the plan and decide\nwhether to implement the fixes.\n\n## Input\n\nBranch name: `[BRANCH_NAME]`\n\n## Steps\n\n1. **Validate Branch**\n - Check current branch matches `[BRANCH_NAME]`\n - If mismatch, STOP with checkout instructions\n\n2. **Fetch PR Data**\n - Search for PR: `repo:vcf/dsm-ui head:[BRANCH_NAME] is:pr`\n - Extract PR number\n - Fetch review comments and summaries\n - If no PR/reviews found, STOP with clear message\n\n3. **Analyze Comments**\n - Categorize as **Actionable** (clear fix) or **Skipped** (questions, unclear, approvals)\n - Create organized list of actionable items with file paths and line numbers\n\n4. **Generate Fix Plan**\n - For each actionable item:\n - Read affected file (if needed for context)\n - Analyze the issue and review comment\n - Propose specific fix following `.cursor/rules/` standards\n - Identify potential impact and risks\n - Estimate complexity (simple/moderate/complex)\n\n - Group fixes by file for better organization\n\n5. **Present Fix Plan**\n - Display comprehensive plan with:\n - **PR Information**: PR number, title, branch\n - **Summary**: Total actionable items, skipped items\n - **Fix Plan by File**:\n - File path\n - Line number(s)\n - Review comment\n - Proposed fix description\n - Code snippet (before/after if applicable)\n - Complexity estimate\n - Potential risks/considerations\n - **Skipped Comments**: List with reasons\n - **Next Steps**: Instructions for author\n\n6. **Author Decision**\n - Author reviews the plan\n - Author can:\n - Accept all fixes (implement manually or ask AI to implement specific ones)\n - Accept some fixes (cherry-pick which to implement)\n - Reject and handle manually\n - Ask for clarification on specific fixes\n\n## Output Format\n\n````markdown\n# Fix Plan for PR #[NUMBER]: [PR_TITLE]\n\n**Branch**: [BRANCH_NAME] **Total Actionable Items**: [COUNT] **Skipped Items**: [COUNT]\n\n---\n\n## Actionable Fixes\n\n### 📁 [file1.ts]\n\n#### Fix 1: [Brief description]\n\n- **Line(s)**: [LINE_NUMBER]\n- **Complexity**: [Simple/Moderate/Complex]\n- **Review Comment**:\n > [Original review comment]\n- **Proposed Fix**: [Detailed description of what needs to be changed and why]\n- **Code Change**:\n\n ```typescript\n // Before:\n [current code]\n\n // After:\n [proposed code]\n ```\n````\n\n- **Considerations**: [Any risks, dependencies, or things to watch out for]\n\n---\n\n### 📁 [file2.ts]\n\n[Similar structure for each file]\n\n---\n\n## Skipped Comments\n\n1. **[file.ts:LINE]** - [Reason for skipping]\n > [Comment text]\n\n---\n\n## Next Steps\n\n1. Review the fix plan above\n2. For fixes you want to implement:\n - Implement manually, or\n - Ask: \"Implement fix [number] from the plan\"\n3. Run linting: `npx nx lint [affected-projects]`\n4. Test your changes\n5. Commit with appropriate message\n6. Push when ready\n\n**Note**: No changes have been made to your code. This is a plan only.\n\n```\n\n## Notes\n\n- **No automatic fixes** - generates plan only\n- **No commits** - author decides when to commit\n- **No code changes** - read-only analysis\n- Only analyze clear, actionable comments\n- Follow all project standards from `.cursor/rules/`\n- Author maintains full control over implementation\n```", "variables": [], "notes": "Generates a fix plan for actionable code review comments from a GitHub PR. The author can review the plan and decide whether to implement the fixes.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/wghglory/ngx-lift-workspace", "path": ".cursor/commands/fix-pr.md", "ref": "2d7e77cc64bc938d35adad34a07ae2dc2bd162b4", "url": "https://github.com/wghglory/ngx-lift-workspace/blob/2d7e77cc64bc938d35adad34a07ae2dc2bd162b4/.cursor/commands/fix-pr.md", "key": "wghglory/ngx-lift-workspace/.cursor/commands/fix-pr.md" } } }

fix-pr

About

Fix PR Review Comments - Plan Mode

Input

Steps

Output Format

📁 [file2.ts]

Skipped Comments

Next Steps

Install fix-pr and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews