Back to Details

create-issue

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
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.
注意：如果你本地安装了
mcporter
，请使用
mcporter
调用MCP工具，不要直接调用MCP工具。
mcporter
CLI提供了更便捷的操作接口和更完善的错误处理能力。

Create Issue via Gitee MCP

通过Gitee MCP创建Issue

Create a well-structured Issue on Gitee after clarifying the requirements with the user. This skill is designed for discussions about new requirements, improvements, or bug reports before they are formally created as Issues.
在与用户明确需求后，在Gitee上创建结构规范的Issue。此技能适用于在正式创建Issue前，针对新需求、功能优化或Bug报告进行讨论的场景。

Prerequisites

前置条件

  • Gitee MCP Server configured (tools: 
    create_issue
    , 
    list_repo_issues
    , 
    list_user_repos
    , 
    search_open_source_repositories
    )
  • User must provide: repository owner/name (or search/select from available repositories)
  • Optional: issue type (feature/bug/enhancement), priority, labels
  • 已配置Gitee MCP Server（支持的工具：
    create_issue
    、
    list_repo_issues
    、
    list_user_repos
    、
    search_open_source_repositories
    ）
  • 用户需提供：仓库所属者/仓库名（或从可用仓库中搜索/选择）
  • 可选信息：Issue类型（功能需求/Bug/优化）、优先级、标签

Steps

操作步骤

Step 1: Identify the Target Repository

步骤1：确定目标仓库

If the user hasn't specified a repository, ask which scenario:
Scenario A: User's own/private repository
  • Use 
    list_user_repos
    to list repositories the user has access to
  • Let user select from the list
Scenario B: Open source/public repository
  • Use 
    search_open_source_repositories
    to search for the repository
  • Verify by checking the repository URL format (
    owner/repo
    )
If the user provides a repository directly (format: 
owner/repo
), verify it exists by confirming with the user.
如果用户未指定仓库，询问用户属于以下哪种场景：
场景A：用户自己的/私有仓库
  • 使用
    list_user_repos
    列出用户有权限访问的仓库
  • 让用户从列表中选择
场景B：开源/公开仓库
  • 使用
    search_open_source_repositories
    搜索目标仓库
  • 通过校验仓库URL格式（
    所有者/仓库名
    ）确认正确性
如果用户直接提供了仓库（格式：
所有者/仓库名
），与用户确认该仓库是否存在。

Step 2: Clarify the Issue Content

步骤2：明确Issue内容

Discuss with the user to gather the following information:
For Bug Reports:
  • What is the expected behavior?
  • What is the actual behavior?
  • How to reproduce the issue (reproduction steps)?
  • Environment details (OS, version, browser, etc.)
  • Any error messages or logs?
For Feature Requests:
  • What problem does this feature solve?
  • What is the proposed solution?
  • Are there any similar features in other projects for reference?
  • Any design preferences or constraints?
For Improvements:
  • What aspect needs improvement?
  • What are the suggested improvements?
  • What is the expected outcome?
Use the following template to structure the discussion:
undefined
与用户沟通收集以下信息：
Bug报告所需信息：
  • 预期行为是什么？
  • 实际行为是什么？
  • 如何复现该问题（复现步骤）？
  • 环境详情（操作系统、版本、浏览器等）
  • 是否有错误信息或日志？
功能需求所需信息：
  • 该功能要解决什么问题？
  • 建议的解决方案是什么？
  • 其他项目中是否有类似功能可参考？
  • 是否有设计偏好或约束条件？
功能优化所需信息：
  • 需要优化哪个方面？
  • 建议的优化措施是什么？
  • 预期的优化效果是什么？
使用以下模板结构化梳理沟通内容：
undefined

Issue Information

Issue Information

Type: [Bug / Feature / Enhancement / Question / Other]
Title: [Brief description - keep it under 50 characters]
Description: [Detailed description of the issue]
Reproduction Steps (for bugs):
  1. Step 1
  2. Step 2
  3. Step 3
Expected Behavior: [What should happen]
Actual Behavior: [What actually happens]
Environment:
  • OS:
  • Version:
  • Browser (if applicable):
Additional Context: [Any other relevant information, screenshots, logs, etc.]
undefined
Type: [Bug / Feature / Enhancement / Question / Other]
Title: [Brief description - keep it under 50 characters]
Description: [Detailed description of the issue]
Reproduction Steps (for bugs):
  1. Step 1
  2. Step 2
  3. Step 3
Expected Behavior: [What should happen]
Actual Behavior: [What actually happens]
Environment:
  • OS:
  • Version:
  • Browser (if applicable):
Additional Context: [Any other relevant information, screenshots, logs, etc.]
undefined

Step 3: Validate and Refine

步骤3：校验与完善

Before creating the Issue:
  1. Check if a similar Issue already exists using 
    list_repo_issues
  2. If duplicates are found, present them to the user
  3. Refine the title and description based on discussion
  4. Confirm with the user before creating
创建Issue前：
  1. 使用
    list_repo_issues
    检查是否已存在类似Issue
  2. 如果发现重复Issue，告知用户
  3. 根据沟通结果优化标题和描述
  4. 创建前与用户确认信息无误

Step 4: Create the Issue

步骤4：创建的Issue

Use 
create_issue
to create the Issue with the following parameters:
  • owner
    : repository owner
  • repo
    : repository name
  • title
    : Issue title (concise and descriptive)
  • body
    : Issue description (detailed and well-structured)
  • labels
    : (optional) comma-separated list of labels like 
    bug
    , 
    feature
    , 
    enhancement
Label recommendations:
TypeLabels
Bug
bug
Feature
feature
Enhancement
enhancement
Question
question
Documentation
docs
使用
create_issue
创建Issue，传入以下参数：
  • owner
    ：仓库所有者
  • repo
    ：仓库名称
  • title
    ：Issue标题（简洁清晰，描述准确）
  • body
    ：Issue描述（内容详尽，结构规范）
  • labels
    ：（可选）逗号分隔的标签列表，如
    bug
    、
    feature
    、
    enhancement
标签推荐：
类型标签
Bug
bug
功能需求
feature
优化
enhancement
问题咨询
question
文档
docs

Step 5: Confirm and Summary

步骤5：确认与总结

After successful creation:
  1. Display the Issue URL to the user
  2. Summarize what was created
  3. Ask if the user wants to:
    • Start implementing (use 
      implement-issue
      skill)
创建成功后：
  1. 向用户展示Issue的URL
  2. 总结已创建的Issue内容
  3. 询问用户是否需要：
    • 开始实现该需求（使用
      implement-issue
      技能）

Example Conversations

对话示例

Example 1: Bug Report
User: I found a bug in the login page - it doesn't show error message when password is wrong.

You: Let me help you create a bug report. Could you please clarify:
1. What is the expected behavior? (e.g., "Show 'Invalid credentials' message")
2. What is the actual behavior? (e.g., "Nothing happens, page just reloads")
3. How to reproduce? (e.g., "Enter wrong password and click login")
4. What browser and OS are you using?

User: [Provides details...]

You: Here's the Issue I've prepared:
Title: Login page doesn't show error message for invalid credentials
...
Should I create this Issue?
Example 2: Feature Request
User: I want to add dark mode to the app.

You: Great idea! Let me understand more about this feature:
1. What problem does dark mode solve? (e.g., "Reduce eye strain at night")
2. Should it follow system preference or be user-toggleable?
3. Any reference implementations you have in mind?

User: [Provides details...]

You: Here's the Issue I've prepared:
Title: Add dark mode support
...
Should I create this Issue?
示例1：Bug报告
User: 我发现登录页面有个Bug——密码输错的时候不会显示错误提示。

You: 我来帮你创建Bug报告，麻烦你补充以下信息：
1. 预期行为是什么？（比如“显示'账号或密码错误'提示”）
2. 实际行为是什么？（比如“页面没有任何反应，只是重新加载”）
3. 复现步骤是什么？（比如“输入错误密码后点击登录按钮”）
4. 你使用的浏览器和操作系统是什么？

User: [提供相关信息...]

You: 这是我整理好的Issue内容：
Title: 登录页面输入错误凭证时未显示错误提示
...
是否确认创建该Issue？
示例2：功能需求
User: 我想给应用加个暗黑模式。

You: 好主意！我需要再了解下这个功能的相关信息：
1. 暗黑模式要解决什么问题？（比如“减少夜间使用时的眼部疲劳”）
2. 应该跟随系统设置还是支持用户手动切换？
3. 有没有你觉得不错的参考实现？

User: [提供相关信息...]

You: 这是我整理好的Issue内容：
Title: 新增暗黑模式支持
...
是否确认创建该Issue？

Notes

注意事项

  • Always confirm the Issue details with the user before creating it
  • Search for existing Issues first to avoid duplicates
  • Use clear, descriptive titles that summarize the issue in one line
  • Include all necessary details in the description to help others understand and reproduce
  • For complex features, consider creating a technical design document as a comment after the Issue is created
  • If the user wants to immediately work on the Issue, suggest using the 
    implement-issue
    skill afterwards
  • 创建Issue前务必与用户确认所有信息无误
  • 先搜索已存在的Issue，避免重复提交
  • 使用清晰、描述性的标题，能一句话总结Issue内容
  • 描述中包含所有必要信息，方便其他开发者理解和复现问题
  • 对于复杂功能，可在Issue创建后作为评论补充技术设计文档
  • 如果用户想要立即处理该Issue，建议后续使用
    implement-issue
    技能