做什么
当用户要求审查一个PR,做代码审查,检查拉动请求,"审查这个PR","审查-pr",或"查看这个拉动请求"时,使用这一技能. 需要Gite MCP 软件 要配置的服务器 .
技能库 智客分类:Agent 工作流 review-pr
当用户要求审查一个PR,做代码审查,检查拉动请求,"审查这个PR","审查-pr",或"查看这个拉动请求"时,使用这一技能. 需要Gite MCP 软件 要配置的服务器 .
官方网址:skills.sh
先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。
当用户要求审查一个PR,做代码审查,检查拉动请求,"审查这个PR","审查-pr",或"查看这个拉动请求"时,使用这一技能. 需要Gite MCP 软件 要配置的服务器 .
官方 description 未单独写出 Use when。按规范,代理会在用户任务与这段 description 的关键词匹配时激活本技能。
按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Review PR via Gitee MCP、Prerequisites、Steps、Step 1: Fetch PR Details、Step 2: Fetch Diff Files、Step 3: Check Existing Comments。 其中含规范建议的小节:分步指令。
文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。
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.
Review PR via Gitee MCPPrerequisitesStepsStep 1: Fetch PR DetailsStep 2: Fetch Diff FilesStep 3: Check Existing CommentsStep 4: Code ReviewStep 5: Classify IssuesStep 6: Present Review to UserCode Review Preview🔴 Blockers🟡 Suggestions
来源分类:skills.sh agent-skill
namereview-prdescription具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗
先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。
复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。
把 Agent Skill「review-pr」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-099614e2282a555a-%E5%AE%A1%E6%9F%A5-Pr.html 请存为 .cursor/skills/review-pr/SKILL.md 或 .claude/skills/review-pr/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。
npx skills add 'https://github.com/oschina/gitee-agent-skills' --list
npx skills add 'https://github.com/oschina/gitee-agent-skills' --skill 'review-pr'
CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。
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.
Perform a thorough code review on a Pull Request in a Gitee repository.
get_pull_detail, get_diff_files, list_comments (resource_type: pull), create_comment (resource_type: pull))Use get_pull_detail to retrieve PR information, checking:
Use get_diff_files to get the list of changed files, analyzing:
For each core changed file, use get_file_content to read its content for context.
If running in the local repository directory, leverage local git commands and file access to gain additional context for the review (e.g., viewing related commits, related files, file history).
Use list_comments (resource_type: pull) to retrieve existing comments and avoid raising issues that have already been discussed.
Review the code across these dimensions:
Correctness
Security
Maintainability
Performance
Consistency
Classify findings by severity:
STOP — Do not post yet!
Present the review content to the user for confirmation. Use this format:
## Code Review Preview
**Summary**: [One sentence describing the purpose of the PR and overall quality assessment]
### 🔴 Blockers
1. **[filename:line]** [Issue description]
- Problem: [Specific explanation]
- Suggestion: [How to fix it]
### 🟡 Suggestions
1. **[filename]** [Issue description]
- Suggestion: [Direction for improvement]
### 🟢 Optional
1. [Improvement suggestion]
### Conclusion
[Overall assessment — LGTM or key changes needed]
If no issues are found, show:
## Code Review Preview
LGTM! No significant issues found. Code quality looks good.
Then ask the user: "请确认以上评审内容是否有问题。确认无误后,我将提交到 PR。"
Once the user confirms the review content is correct, use create_comment (resource_type: pull) to post the review to the PR. Use this format:
## Code Review
**Summary**: [One sentence describing the purpose of the PR and overall quality assessment]
### 🔴 Blockers
1. **[filename:line]** [Issue description]
- Problem: [Specific explanation]
- Suggestion: [How to fix it]
### 🟡 Suggestions
1. **[filename]** [Issue description]
- Suggestion: [Direction for improvement]
### 🟢 Optional
1. [Improvement suggestion]
### Conclusion
[Overall assessment — LGTM or key changes needed]
🤖 Generated by AI + Gitee MCP
If no issues are found, comment:
## Code Review
LGTM! No significant issues found. Code quality looks good.
🤖 Generated by AI + Gitee MCP
Agent 工作流
创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.
Agent 工作流
使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.
Agent 工作流
管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.
Agent 工作流
Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…