Back to Details

implement-issue

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Implement Issue via Gitee MCP

通过Gitee MCP处理Issue

Complete the full development loop starting from a Gitee Issue: requirements analysis → coding → creating a PR → linking back to the Issue.
完成从Gitee Issue开始的完整开发流程：需求分析 → 编码 → 创建PR → 关联回Issue。

Prerequisites

前置条件

  • Gitee MCP Server configured (tools: 
    get_repo_issue_detail
    , 
    list_repo_issues
    , 
    create_pull
    , 
    comment_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.
  • 已配置Gitee MCP Server（涉及工具：
    get_repo_issue_detail
    、
    list_repo_issues
    、
    create_pull
    、
    comment_issue
    、
    update_issue
    ）
  • 用户必须提供：仓库所有者、仓库名称、Issue编号（或从列表中选择）
  • 本地仓库路径：本技能需在该Issue对应仓库的本地检出目录中执行，或用户需提供仓库克隆的本地路径。这是Coding Agent读取和修改源文件的必要条件。

Steps

操作步骤

Step 1: Fetch Issue Details

步骤1：获取Issue详情

Use 
get_repo_issue_detail
to retrieve full Issue information:
  • Title and full description
  • Labels (feature / bug / enhancement, etc.)
  • Priority and milestone
  • Existing comments (to understand discussion context)
Also use 
list_issue_comments
to review comments and check:
  • Existing technical design discussions
  • Relevant background context
  • Whether someone else is already working on it
使用
get_repo_issue_detail
获取完整的Issue信息：
  • 标题与完整描述
  • 标签（功能需求/缺陷修复/功能优化等）
  • 优先级与里程碑
  • 现有评论（用于理解讨论上下文）
同时使用
list_issue_comments
查看评论，确认：
  • 已有的技术设计讨论
  • 相关背景信息
  • 是否已有其他人在处理该Issue

Step 2: Requirements Analysis

步骤2：需求分析

Based on the Issue content, produce a requirements analysis:
undefined
基于Issue内容，生成需求分析报告：
undefined

Requirements Analysis: [Issue title]

需求分析：[Issue标题]

Type: [Feature / Bug Fix / Performance / Other]
Goal: [One sentence describing what needs to be implemented]
Scope (estimated):
  • [Modules / files likely involved]
  • [APIs / database tables likely involved]
Implementation Plan:
  1. [Step 1]
  2. [Step 2]
  3. [Step 3]
Potential Risks:
  • [Things to watch out for]
Acceptance Criteria:
  • [Criterion 1]
  • [Criterion 2]
undefined
类型：[功能需求 / 缺陷修复 / 性能优化 / 其他]
目标: [一句话描述需要实现的内容]
范围（预估）:
  • [可能涉及的模块/文件]
  • [可能涉及的API/数据库表]
实现方案:
  1. [步骤1]
  2. [步骤2]
  3. [步骤3]
潜在风险:
  • [需要注意的事项]
验收标准:
  • [标准1]
  • [标准2]
undefined

Step 3: Assist with Implementation

步骤3：协助实现开发

Based on the requirements analysis, help the user by:
  • Providing concrete code implementation approaches
  • Giving code examples for key logic
  • Pointing out which files need to be modified
If the user has already finished coding, proceed to the next step.
基于需求分析结果，为用户提供以下支持：
  • 具体的代码实现思路
  • 核心逻辑的代码示例
  • 指出需要修改的文件
若用户已完成编码，直接进入下一步。

Step 4: Record Progress in the Issue

步骤4：在Issue中记录进度

Use 
comment_issue
to post a progress update on the Issue:
Starting work on this issue. Expected changes:
- [Main change 1]

Implementation approach:
[Brief summary]
This keeps other contributors informed and avoids duplicated effort.
使用
comment_issue
在Issue中发布进度更新：
已开始处理该Issue。预计修改内容：
- [主要修改点1]

实现思路：
[简要说明]
此举可让其他贡献者了解进度，避免重复工作。

Step 5: Create a Linked PR

步骤5：创建关联的PR

Use 
create_pull
to create a PR. The PR description should include:
  • Summary of changes
  • Implementation approach overview
  • Testing notes
  • closes #[issue number]
    (to auto-close the linked Issue on merge)
使用
create_pull
创建PR。PR描述需包含：
  • 修改内容概述
  • 实现思路总览
  • 测试说明
  • closes #[Issue编号]
    （用于在PR合并时自动关闭关联的Issue）

Step 6: Update the Issue

步骤6：更新Issue状态

After the PR is created:
  1. Use 
    comment_issue
    to post the PR link on the Issue
  2. If the Issue status needs updating, use 
    update_issue
    to change it
Comment template:
PR #[PR number] has been created to address this issue.
Please review: [PR link]
PR创建完成后：
  1. 使用
    comment_issue
    在Issue中发布PR链接
  2. 若需更新Issue状态，使用
    update_issue
    进行修改
评论模板：
已创建PR #[PR编号] 以处理该Issue。
请审阅：[PR链接]

Notes

注意事项

  • Before starting, confirm the Issue has not been claimed by someone else (check assignees)
  • For significant design decisions, discuss and confirm in the Issue comments before coding
  • The 
    closes #N
    syntax in the PR description will automatically close the Issue when the PR is merged
  • 开始前，请确认该Issue未被他人认领（检查经办人）
  • 对于重大设计决策，需在编码前在Issue评论区讨论并确认
  • PR描述中的
    closes #N
    语法会在PR合并时自动关闭对应的Issue