Note: If you have mcporter installed locally, you should use mcporter to invoke the MCP tool instead of directly calling the MCP tool. The mcporter CLI provides a more convenient interface and better error handling.

Implement Issue via Gitee MCP

Complete the full development loop starting from a Gitee Issue: requirements analysis → coding → creating a PR → linking back to the Issue.

Prerequisites

• Gitee MCP Server configured (tools: get_repo_issue_detail, list_repo_issues, create_pull, create_comment (resource_type: issue), update_issue)
• User must provide: repository owner, repository name, Issue number (or select from a list)
• Local repository path: This skill must be executed in the local checkout of the issue's repository, OR the user must provide the local path to the repository clone. This is required for the Coding Agent to read and modify source files.

Steps

Step 1: Fetch Issue Details