refactor: update issue-fixer mode to use GitHub CLI instead of MCP (#5320)

.roo/rules-issue-fixer/1_Workflow.xml

@@ -1,62 +1,41 @@
 <workflow>
   <step number="1">
-    <name>Determine Workflow Type and Retrieve Context</name>
+    <name>Retrieve Issue Context</name>
     <instructions>
-      First, determine what type of work is needed. The user will provide either:
-      - An issue number/URL (e.g., "#123" or GitHub issue URL) - for new implementation
-      - A PR number/URL (e.g., "#456" or GitHub PR URL) - for addressing review feedback
-      - A description of changes needed for an existing PR
-      
-      For Issue-based workflow:
-      Extract the issue number and retrieve it:
-      
-      <use_mcp_tool>
-      <server_name>github</server_name>
-      <tool_name>get_issue</tool_name>
-      <arguments>
-      {
-        "owner": "RooCodeInc",
-        "repo": "Roo-Code",
-        "issue_number": [extracted number]
-      }
-      </arguments>
-      </use_mcp_tool>
-      
-      For PR Review workflow:
-      Extract the PR number and retrieve it:
-      
-      <use_mcp_tool>
-      <server_name>github</server_name>
-      <tool_name>get_pull_request</tool_name>
-      <arguments>
-      {
-        "owner": "RooCodeInc",
-        "repo": "Roo-Code",
-        "pull_number": [extracted number]
-      }
-      </arguments>
-      </use_mcp_tool>
-      
-      Then get PR review comments:
-      
-      <use_mcp_tool>
-      <server_name>github</server_name>
-      <tool_name>get_pull_request_reviews</tool_name>
-      <arguments>
-      {
-        "owner": "RooCodeInc",
-        "repo": "Roo-Code",
-        "pull_number": [extracted number]
-      }
-      </arguments>
-      </use_mcp_tool>
-      
-      Analyze the context to determine:
-      1. Type of work (new issue implementation vs PR feedback)
-      2. All requirements and acceptance criteria
-      3. Specific changes requested (for PR reviews)
-      4. Technical details mentioned
-      5. Any linked issues or discussions
+      The user should provide a full GitHub issue URL (e.g., "https://github.com/owner/repo/issues/123") for implementation.
+      
+      Parse the URL to extract:
+      - Owner (organization or username)
+      - Repository name
+      - Issue number
+      
+      For example, from https://github.com/RooCodeInc/Roo-Code/issues/123:
+      - Owner: RooCodeInc
+      - Repo: Roo-Code
+      - Issue: 123
+      
+      Then retrieve the issue:
+      
+      <execute_command>
+      <command>gh issue view [issue-number] --repo [owner]/[repo] --json number,title,body,state,labels,assignees,milestone,createdAt,updatedAt,closedAt,author</command>
+      </execute_command>
+      
+      If the command fails with an authentication error (e.g., "gh: Not authenticated" or "HTTP 401"), ask the user to authenticate:
+      <ask_followup_question>
+      <question>GitHub CLI is not authenticated. Please run 'gh auth login' in your terminal to authenticate, then let me know when you're ready to continue.</question>
+      <follow_up>
+      <suggest>I've authenticated, please continue</suggest>
+      <suggest>I need help with authentication</suggest>
+      <suggest>Let's use a different approach</suggest>
+      </follow_up>
+      </ask_followup_question>
+      
+      Analyze the issue to determine:
+      1. All requirements and acceptance criteria
+      2. Technical details mentioned
+      3. Any linked issues or discussions
+      
+      Note: For PR review feedback, users should use the dedicated pr-fixer mode instead.
     </instructions>
   </step>
 
@@ -69,23 +48,20 @@
       - Community suggestions
       - Any decisions or changes to requirements
       
-      <use_mcp_tool>
-      <server_name>github</server_name>
-      <tool_name>get_issue_comments</tool_name>
-      <arguments>
-      {
-        "owner": "RooCodeInc",
-        "repo": "Roo-Code",
-        "issue_number": [issue number]
-      }
-      </arguments>
-      </use_mcp_tool>
+      <execute_command>
+      <command>gh issue view [issue number] --repo [owner]/[repo] --comments</command>
+      </execute_command>
       
       Also check for:
       1. Related issues mentioned in the body or comments
       2. Linked pull requests
       3. Referenced discussions
       
+      If related PRs are mentioned, view them:
+      <execute_command>
+      <command>gh pr view [pr-number] --repo [owner]/[repo]</command>
+      </execute_command>
+      
       Document all requirements and constraints found.
     </instructions>
   </step>
@@ -109,16 +85,9 @@
       - Identify patterns to follow
       - Find related components and utilities
       
-      For PR Reviews:
-      - Search for files mentioned in review comments
-      - Find related files that use similar patterns
-      - Locate test files for modified functionality
-      - Identify files that import/depend on changed code
-      
       Example searches based on issue type:
       - Bug: Search for error messages, function names, component names
       - Feature: Search for similar functionality, API endpoints, UI components
-      - PR Review: Search for patterns mentioned in feedback
       
       CRITICAL: Always read multiple related files together to understand:
       - Current code patterns and conventions
@@ -133,10 +102,15 @@
       - read_file to examine specific implementations (read multiple files at once)
       - search_files for specific patterns or error messages
       
-      Also use GitHub tools:
-      - list_commits to see recent changes to affected files
-      - get_commit to understand specific changes
-      - list_pull_requests to find related PRs
+      Also use GitHub CLI to check recent changes:
+      <execute_command>
+      <command>gh api repos/[owner]/[repo]/commits?path=[file-path]&per_page=10 --jq '.[].sha + " " + .[].commit.message'</command>
+      </execute_command>
+      
+      Search for related PRs:
+      <execute_command>
+      <command>gh pr list --repo [owner]/[repo] --search "[relevant search terms]" --limit 10</command>
+      </execute_command>
       
       Document:
       - All files that need modification
@@ -464,13 +438,13 @@
 
       **Branch:** [branch-name]
       **Title:** [PR title]
-      **Target:** RooCodeInc/Roo-Code (main branch)
+      **Target:** [owner]/[repo] (main branch)
 
       Here's the PR description:
 
       [Show prepared PR description]
 
-      Would you like me to create this pull request to RooCodeInc/Roo-Code?</question>
+      Would you like me to create this pull request to [owner]/[repo]?</question>
       <follow_up>
       <suggest>Yes, create the pull request</suggest>
       <suggest>Let me review the PR description first</suggest>
@@ -484,46 +458,28 @@
   <step number="11">
     <name>Create Pull Request</name>
     <instructions>
-      Once user approves, create the pull request using GitHub MCP:
-      
-      <use_mcp_tool>
-      <server_name>github</server_name>
-      <tool_name>create_pull_request</tool_name>
-      <arguments>
-      {
-        "owner": "RooCodeInc",
-        "repo": "Roo-Code",
-        "title": "[Type]: [Brief description] (#[issue-number])",
-        "head": "[user-fork-owner]:[branch-name]",
-        "base": "main",
-        "body": "[Complete PR description from step 9]",
-        "draft": false,
-        "maintainer_can_modify": true
-      }
-      </arguments>
-      </use_mcp_tool>
-      
-      Note: The "head" parameter format depends on where the branch exists:
-      - If user has push access: "branch-name"
-      - If working from a fork: "username:branch-name"
+      Once user approves, create the pull request using GitHub CLI:
+      
+      If the user doesn't have push access to [owner]/[repo], fork the repository:
+      <execute_command>
+      <command>gh repo fork [owner]/[repo] --clone</command>
+      </execute_command>
+      
+      Create the pull request:
+      <execute_command>
+      <command>gh pr create --repo [owner]/[repo] --base main --title "[Type]: [Brief description] (#[issue-number])" --body "[Complete PR description from step 10]" --maintainer-can-modify</command>
+      </execute_command>
+      
+      The gh CLI will automatically handle the fork workflow if needed.
       
       After PR creation:
-      1. Capture the PR number and URL from the response
+      1. Capture the PR number and URL from the command output
       2. Link the PR to the issue by commenting on the issue
       3. Inform the user of the successful creation
       
-      <use_mcp_tool>
-      <server_name>github</server_name>
-      <tool_name>add_issue_comment</tool_name>
-      <arguments>
-      {
-        "owner": "RooCodeInc",
-        "repo": "Roo-Code",
-        "issue_number": [original issue number],
-        "body": "PR #[new PR number] has been created to address this issue: [PR URL]"
-      }
-      </arguments>
-      </use_mcp_tool>
+      <execute_command>
+      <command>gh issue comment [original issue number] --repo [owner]/[repo] --body "PR #[new PR number] has been created to address this issue: [PR URL]"</command>
+      </execute_command>
       
       Final message to user:
       ```
@@ -550,7 +506,7 @@
       After the PR is created, monitor the CI/CD checks to ensure they pass:
       
       <execute_command>
-      <command>gh pr checks --watch</command>
+      <command>gh pr checks [PR number] --repo [owner]/[repo] --watch</command>
       </execute_command>
       
       This command will:

.roo/rules-issue-fixer/4_github_cli_usage.xml

@@ -0,0 +1,221 @@
+<github_cli_usage>
+  <overview>
+    This mode uses the GitHub CLI (gh) for all GitHub operations.
+    The mode assumes the user has gh installed and authenticated. If authentication errors occur,
+    the mode will prompt the user to authenticate.
+    
+    Users must provide full GitHub issue URLs (e.g., https://github.com/owner/repo/issues/123)
+    so the mode can extract the repository information dynamically.
+  </overview>
+  
+  <url_parsing>
+    <pattern>https://github.com/[owner]/[repo]/issues/[number]</pattern>
+    <extraction>
+      - Owner: The organization or username
+      - Repo: The repository name
+      - Number: The issue number
+    </extraction>
+  </url_parsing>
+
+  <authentication_handling>
+    <approach>Assume authenticated, handle errors gracefully</approach>
+    <when>Only check authentication if a gh command fails with auth error</when>
+    <error_patterns>
+      - "gh: Not authenticated"
+      - "HTTP 401"
+      - "HTTP 403: Resource not accessible"
+    </error_patterns>
+  </authentication_handling>
+
+  <primary_commands>
+    <command name="gh_issue_view">
+      <purpose>Retrieve the issue details at the start</purpose>
+      <when>Always use first to get the full issue content</when>
+      <syntax>gh issue view [issue-number] --repo [owner]/[repo] --json number,title,body,state,labels,assignees,milestone,createdAt,updatedAt,closedAt,author</syntax>
+      <example>
+        <execute_command>
+        <command>gh issue view 123 --repo octocat/hello-world --json number,title,body,state,labels,assignees,milestone,createdAt,updatedAt,closedAt,author</command>
+        </execute_command>
+      </example>
+    </command>
+    
+    <command name="gh_issue_comments">
+      <purpose>Get additional context and requirements from issue comments</purpose>
+      <when>Always use after viewing issue to see full discussion</when>
+      <syntax>gh issue view [issue-number] --repo [owner]/[repo] --comments</syntax>
+      <example>
+        <execute_command>
+        <command>gh issue view 123 --repo octocat/hello-world --comments</command>
+        </execute_command>
+      </example>
+    </command>
+    
+    
+    <command name="gh_repo_view_commits">
+      <purpose>Find recent changes to affected files</purpose>
+      <when>Use during codebase exploration</when>
+      <syntax>gh api repos/[owner]/[repo]/commits?path=[file-path]&per_page=10</syntax>
+      <example>
+        <execute_command>
+        <command>gh api repos/octocat/hello-world/commits?path=src/api/index.ts&per_page=10 --jq '.[].sha + " " + .[].commit.message'</command>
+        </execute_command>
+      </example>
+    </command>
+    
+    <command name="gh_search_code">
+      <purpose>Search for code patterns on GitHub</purpose>
+      <when>Use to supplement local codebase_search</when>
+      <syntax>gh search code "[search-query]" --repo [owner]/[repo]</syntax>
+      <example>
+        <execute_command>
+        <command>gh search code "function handleError" --repo octocat/hello-world --limit 10</command>
+        </execute_command>
+      </example>
+    </command>
+  </primary_commands>
+  
+  <optional_commands>
+    <command name="gh_issue_comment">
+      <purpose>Add progress updates or ask questions on issues</purpose>
+      <when>Use if clarification needed or to show progress</when>
+      <syntax>gh issue comment [issue-number] --repo [owner]/[repo] --body "[comment]"</syntax>
+      <example>
+        <execute_command>
+        <command>gh issue comment 123 --repo octocat/hello-world --body "Working on this issue. Found the root cause in the theme detection logic."</command>
+        </execute_command>
+      </example>
+    </command>
+    
+    <command name="gh_pr_list">
+      <purpose>Find related or similar PRs</purpose>
+      <when>Use to understand similar changes</when>
+      <syntax>gh pr list --repo [owner]/[repo] --search "[search-terms]"</syntax>
+      <example>
+        <execute_command>
+        <command>gh pr list --repo octocat/hello-world --search "dark theme" --limit 10</command>
+        </execute_command>
+      </example>
+    </command>
+    
+    <command name="gh_pr_diff">
+      <purpose>View the diff of a pull request</purpose>
+      <when>Use to understand changes in a PR</when>
+      <syntax>gh pr diff [pr-number] --repo [owner]/[repo]</syntax>
+      <example>
+        <execute_command>
+        <command>gh pr diff 456 --repo octocat/hello-world</command>
+        </execute_command>
+      </example>
+    </command>
+  </optional_commands>
+  
+  <pull_request_commands>
+    <command name="gh_pr_create">
+      <purpose>Create a pull request</purpose>
+      <when>Use in step 11 after user approval</when>
+      <important>
+        - Target the repository from the provided URL
+        - Use "main" as the base branch unless specified otherwise
+        - Include issue number in PR title
+        - Use --maintainer-can-modify flag
+      </important>
+      <syntax>gh pr create --repo [owner]/[repo] --base main --title "[title]" --body "[body]" --maintainer-can-modify</syntax>
+      <example>
+        <execute_command>
+        <command>gh pr create --repo octocat/hello-world --base main --title "fix: Resolve dark theme button visibility (#123)" --body "## Description
+
+Fixes #123
+
+[Full PR description]" --maintainer-can-modify</command>
+        </execute_command>
+      </example>
+      <note>
+        If working from a fork, ensure the fork is set as the remote and push the branch there first.
+        The gh CLI will automatically handle the fork workflow.
+      </note>
+    </command>
+    
+    <command name="gh_repo_fork">
+      <purpose>Fork the repository if user doesn't have push access</purpose>
+      <when>Use if user needs to work from a fork</when>
+      <syntax>gh repo fork [owner]/[repo] --clone</syntax>
+      <example>
+        <execute_command>
+        <command>gh repo fork octocat/hello-world --clone</command>
+        </execute_command>
+      </example>
+    </command>
+    
+    <command name="gh_pr_checks">
+      <purpose>Monitor CI/CD checks on a pull request</purpose>
+      <when>Use after creating PR to ensure checks pass</when>
+      <syntax>gh pr checks [pr-number] --repo [owner]/[repo] --watch</syntax>
+      <example>
+        <execute_command>
+        <command>gh pr checks 789 --repo octocat/hello-world --watch</command>
+        </execute_command>
+      </example>
+    </command>
+  </pull_request_commands>
+  
+  <workflow_helpers>
+    <command name="gh_api">
+      <purpose>Access GitHub API directly for advanced operations</purpose>
+      <when>Use when specific gh commands don't provide needed functionality</when>
+      <examples>
+        <!-- Get repository information -->
+        <execute_command>
+        <command>gh api repos/[owner]/[repo] --jq '.default_branch'</command>
+        </execute_command>
+        
+        <!-- Get file contents -->
+        <execute_command>
+        <command>gh api repos/[owner]/[repo]/contents/README.md --jq '.content' | base64 -d</command>
+        </execute_command>
+        
+        <!-- Get workflow runs -->
+        <execute_command>
+        <command>gh api repos/[owner]/[repo]/actions/runs --jq '.workflow_runs[0:5] | .[] | .id, .status, .conclusion'</command>
+        </execute_command>
+      </examples>
+    </command>
+    
+    <command name="gh_run_list">
+      <purpose>Check GitHub Actions workflow status</purpose>
+      <when>Use to monitor CI/CD pipeline</when>
+      <syntax>gh run list --repo [owner]/[repo] --limit 5</syntax>
+      <example>
+        <execute_command>
+        <command>gh run list --repo octocat/hello-world --limit 5</command>
+        </execute_command>
+      </example>
+    </command>
+  </workflow_helpers>
+  
+  <error_handling>
+    <scenario name="not_authenticated">
+      <error>gh: Not authenticated. Run 'gh auth login' to authenticate.</error>
+      <action>
+        Ask user to authenticate:
+        <ask_followup_question>
+        <question>GitHub CLI is not authenticated. Please run 'gh auth login' in your terminal to authenticate, then let me know when you're ready to continue.</question>
+        <follow_up>
+        <suggest>I've authenticated, please continue</suggest>
+        <suggest>I need help with authentication</suggest>
+        <suggest>Let's use a different approach</suggest>
+        </follow_up>
+        </ask_followup_question>
+      </action>
+    </scenario>
+    
+    <scenario name="no_permissions">
+      <error>HTTP 403: Resource not accessible by integration</error>
+      <action>
+        Check if working from a fork is needed:
+        <execute_command>
+        <command>gh repo fork [owner]/[repo] --clone</command>
+        </execute_command>
+      </action>
+    </scenario>
+  </error_handling>
+</github_cli_usage>

.roo/rules-issue-fixer/4_github_mcp_tool_usage.xml

@@ -1,88 +0,0 @@
-<github_mcp_tools_usage>
-  <primary_tools>
-    <tool name="get_issue">
-      <purpose>Retrieve the issue details at the start</purpose>
-      <when>Always use first to get the full issue content</when>
-    </tool>
-    
-    <tool name="get_issue_comments">
-      <purpose>Get additional context and requirements</purpose>
-      <when>Always use after get_issue to see full discussion</when>
-    </tool>
-    
-    <tool name="list_commits">
-      <purpose>Find recent changes to affected files</purpose>
-      <when>Use during codebase exploration</when>
-    </tool>
-    
-    <tool name="search_code">
-      <purpose>Find code patterns on GitHub</purpose>
-      <when>Use to supplement local codebase_search</when>
-    </tool>
-  </primary_tools>
-  
-  <optional_tools>
-    <tool name="add_issue_comment">
-      <purpose>Add progress updates or ask questions</purpose>
-      <when>Use if clarification needed or to show progress</when>
-    </tool>
-    
-    <tool name="list_pull_requests">
-      <purpose>Find related or similar PRs</purpose>
-      <when>Use to understand similar changes</when>
-    </tool>
-    
-    <tool name="get_pull_request">
-      <purpose>Get details of related PRs</purpose>
-      <when>Use when issue references specific PRs</when>
-    </tool>
-  </optional_tools>
-  
-  <pull_request_tools>
-    <tool name="create_pull_request">
-      <purpose>Create a pull request to RooCodeInc/Roo-Code</purpose>
-      <when>Use in step 10 after user approval</when>
-      <important>
-        - Always target RooCodeInc/Roo-Code repository
-        - Use "main" as the base branch unless specified otherwise
-        - Include issue number in PR title
-        - Set maintainer_can_modify to true
-      </important>
-      <example>
-        <use_mcp_tool>
-        <server_name>github</server_name>
-        <tool_name>create_pull_request</tool_name>
-        <arguments>
-        {
-          "owner": "RooCodeInc",
-          "repo": "Roo-Code",
-          "title": "fix: Resolve dark theme button visibility (#123)",
-          "head": "username:fix/issue-123-dark-theme-button",
-          "base": "main",
-          "body": "## Description\n\nFixes #123\n\n[Full PR description]",
-          "draft": false,
-          "maintainer_can_modify": true
-        }
-        </arguments>
-        </use_mcp_tool>
-      </example>
-    </tool>
-    
-    <tool name="fork_repository">
-      <purpose>Fork the repository if user doesn't have push access</purpose>
-      <when>Use if user needs to work from a fork</when>
-      <example>
-        <use_mcp_tool>
-        <server_name>github</server_name>
-        <tool_name>fork_repository</tool_name>
-        <arguments>
-        {
-          "owner": "RooCodeInc",
-          "repo": "Roo-Code"
-        }
-        </arguments>
-        </use_mcp_tool>
-      </example>
-    </tool>
-  </pull_request_tools>
-</github_mcp_tools_usage>

.roo/rules-issue-fixer/5_pull_request_workflow.xml

@@ -4,6 +4,7 @@
     2. Push to appropriate branch (fork or direct)
     3. Prepare comprehensive PR description
     4. Get user approval before creating PR
+    5. Extract owner and repo from the provided GitHub URL
   </preparation>
   
   <pr_title_format>
@@ -22,9 +23,30 @@
     - Screenshots/demos if applicable
   </pr_description_template>
   
+  <creating_pr_with_cli>
+    Use GitHub CLI to create the pull request:
+    <execute_command>
+    <command>gh pr create --repo [owner]/[repo] --base main --title "[title]" --body "[description]" --maintainer-can-modify</command>
+    </execute_command>
+    
+    If working from a fork, ensure you've forked first:
+    <execute_command>
+    <command>gh repo fork [owner]/[repo] --clone</command>
+    </execute_command>
+    
+    The gh CLI automatically handles fork workflows.
+  </creating_pr_with_cli>
+  
   <after_creation>
-    1. Comment on original issue with PR link
+    1. Comment on original issue with PR link:
+       <execute_command>
+       <command>gh issue comment [issue-number] --repo [owner]/[repo] --body "PR #[pr-number] has been created to address this issue: [PR URL]"</command>
+       </execute_command>
     2. Inform user of successful creation
     3. Provide next steps and tracking info
+    4. Monitor PR checks:
+       <execute_command>
+       <command>gh pr checks [pr-number] --repo [owner]/[repo] --watch</command>
+       </execute_command>
   </after_creation>
 </pull_request_workflow>

.roo/rules-issue-fixer/8_github_communication_guidelines.xml

@@ -1,14 +1,4 @@
 <github_communication_guidelines>
-  <pr_comments>
-    - Keep comments concise and focused on technical substance
-    - Avoid overly verbose explanations unless specifically requested
-    - Sound human and conversational, not robotic
-    - Address specific feedback points directly
-    - Use bullet points for multiple changes
-    - Reference line numbers or specific code when relevant
-    - Example: "Updated the error handling in `validateInput()` to catch edge cases as requested. Also added the missing null check on line 45."
-  </pr_comments>
-  
   <issue_comments>
     - Provide brief status updates when working on complex issues
     - Ask specific questions if requirements are unclear

.roo/rules-issue-fixer/9_pr_review_workflow.xml

@@ -1,30 +0,0 @@
-<pr_review_workflow>
-  <handling_feedback>
-    When working on PR review feedback:
-    1. Read all review comments carefully
-    2. Identify specific changes requested
-    3. Group related feedback into logical changes
-    4. Address each point systematically
-    5. Test changes thoroughly
-    6. Respond to each review comment when pushing updates
-    7. Use "Resolved" or brief explanations for each addressed point
-  </handling_feedback>
-  
-  <partial_implementation>
-    For partial workflows (user-requested changes to existing PRs):
-    1. Focus only on the specific changes requested
-    2. Don't refactor unrelated code unless explicitly asked
-    3. Maintain consistency with existing PR approach
-    4. Test only the modified functionality unless broader testing is needed
-    5. Update PR description if significant changes are made
-  </partial_implementation>
-  
-  <review_response_format>
-    When responding to review comments:
-    - "✅ Fixed - [brief description of change]"
-    - "✅ Added - [what was added]"
-    - "✅ Updated - [what was changed]"
-    - "❓ Question - [if clarification needed]"
-    - Keep responses short and action-oriented
-  </review_response_format>
-</pr_review_workflow>

.roomodes

@@ -148,16 +148,14 @@ customModes:
        - Building new features based on detailed proposals
        - Ensuring all acceptance criteria are met before completion
        - Creating pull requests with proper documentation
-       - Handling PR review feedback and implementing requested changes
-       - Making concise, human-sounding GitHub comments that focus on technical substance
+       - Using GitHub CLI for all GitHub operations
 
-      You work with issues from the RooCodeInc/Roo-Code repository, transforming them into working code that addresses all requirements while maintaining code quality and consistency. You also handle partial workflows for existing PRs when changes are requested by maintainers or users through the review process.
-    whenToUse: Use this mode when you have a GitHub issue (bug report or feature request) that needs to be fixed or implemented, OR when you need to address feedback on an existing pull request. Provide the issue number, PR number, or URL, and this mode will guide you through understanding the requirements, implementing the solution, and preparing for submission or updates.
+      You work with issues from any GitHub repository, transforming them into working code that addresses all requirements while maintaining code quality and consistency. You use the GitHub CLI (gh) for all GitHub operations instead of MCP tools.
+    whenToUse: Use this mode when you have a GitHub issue (bug report or feature request) that needs to be fixed or implemented. Provide the issue URL, and this mode will guide you through understanding the requirements, implementing the solution, and preparing for submission.
     groups:
       - read
       - edit
       - command
-      - mcp
     source: project
   - slug: issue-writer
     name: 📝 Issue Writer