القائمة
Use this skill when the user asks to create a PR, open a pull request, "create-pr", "submit a pull request", or "open a merge request". Requires Gitee MCP Server to be configured.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use this skill when the user asks to close an issue, wrap up an issue, "close issue", "close-issue-flow", or finish up after a fix has been merged. Requires Gitee MCP Server to be configured.
Use this skill when the user asks to implement an issue, "work on this issue", "implement issue", "develop based on an issue", "implement-issue". Requires Gitee MCP Server to be configured.
Use this skill when the user asks to merge a PR, check if a PR is ready to merge, "merge PR", "can this PR be merged", "merge-pr-check". Requires Gitee MCP Server to be configured.
Use this skill when the user wants to get quick fix suggestions for an issue, "how to fix this issue", "where should I make changes", "quick-fix-suggestion", "suggest fix", "fix suggestion", "how to implement this issue", or before starting implementation to understand the scope of changes. This skill analyzes the issue content, locates relevant code in the repository, and suggests which files to modify with draft implementation plans. Requires Gitee MCP Server to be configured and must be run in a local git repository.
Use this skill when the user asks to review a PR, do a code review, check a pull request, "review this PR", "review-pr", or "look at this pull request". Requires Gitee MCP Server to be configured.
Use this skill when the user wants to check for stale PRs, "find old pull requests", "stale PRs", "PRs needing attention", or wants to identify pull requests that have been inactive for too long. This skill scans repositories for PRs that need action and generates a prioritized reminder report. Requires Gitee MCP Server to be configured.
| name | create-pr |
| description | Use this skill when the user asks to create a PR, open a pull request, "create-pr", "submit a pull request", or "open a merge request". Requires Gitee MCP Server to be configured. |
| version | 1.0.0 |
| requires | {"mcp-servers":["gitee"]} |
Note: If you have
mcporterinstalled locally, you should usemcporterto invoke the MCP tool instead of directly calling the MCP tool. ThemcporterCLI provides a more convenient interface and better error handling.
Generate a well-structured Pull Request description based on the current changes and submit it to Gitee.
create_pull, get_file_content, list_repo_issues, compare_branches_tags)Confirm with the user or infer from context:
Use compare_branches_tags to fetch the diff between the source branch and target branch:
base: target branch (e.g., main or master)head: source branchAnalyze the returned diff to determine:
Follow the Conventional Commits format:
<type>(<scope>): <subject>
Available types:
feat: New featurefix: Bug fixrefactor: Code refactoringdocs: Documentation updatetest: Test-related changeschore: Build / dependency / toolchain changesExample: feat(auth): add OAuth2 login support
Use the following template for a structured description:
## Summary
[Clear description of the purpose of this PR and the problem it solves]
## Changes
- [Change 1]
- [Change 2]
- [Change 3]
## Testing
- [ ] Unit tests pass
- [ ] Functional tests pass
- [x] [Completed test item]
## Related Issue
closes #[issue number] (if applicable)
## Notes
[Breaking changes, dependency upgrades, deployment considerations, etc. (if any)]
Use create_pull to create the PR with these parameters:
title: title generated in Step 3body: description generated in Step 4head: source branchbase: target branchAfter successful creation, output the PR link for the user.
closes #N to the description so the Issue is automatically closed when the PR is merged