npx skills add https://github.com/metabase/metabase --skill docs-review@./../_shared/metabase-style-guide.md
重要:在开始审查之前,请确定使用哪种模式:
PR 审查模式:如果 mcp__github__create_pending_pull_request_review 工具可用,你正在审查一个 GitHub PR
本地审查模式:如果 MCP 工具不可用,则在对话中输出问题
mcp__github__create_pending_pull_request_review 是否可用浏览差异内容,查找以下问题:
语气和口吻:
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
结构和清晰度:
链接和引用:
格式:
代码和示例:
句子结构:
| 模式 | 问题 |
|---|---|
| we can do X, our feature | 应为“Metabase”或“it” |
| click here, read more here | 需要描述性的链接文本 |
| easy, simple, just | 移除居高临下的限定词 |
| users | 如果可能,应为“people”或“companies” |
强制要求:每个问题都必须从问题 1 开始顺序编号。
此编号格式是不可协商的。它允许用户高效地引用特定问题(例如,“修复问题 1、3 和 5”)并跟踪哪些反馈已得到处理。
在对话中输出问题(本地模式)时,使用此格式:
## 问题
**问题 1: [简要标题]**
第 X 行:问题的简要描述
[代码或示例]
建议的修复或简要解释
**问题 2: [简要标题]**
第 Y 行:问题的描述
建议的修复或解释
**问题 3: [简要标题]**
...
示例:
问题 1: 正式语气 第 15 行:这可以更口语化一些。考虑使用:“You can't...” 而不是 “You cannot...”
问题 2: 模糊标题 第 8 行:标题可以更具体。尝试直接陈述要点:“Run migrations before upgrading” 对比 “Upgrade process”
发布到 GitHub(PR 模式)时,使用待处理审查工作流:
工作流步骤:
开始审查:使用 mcp__github__create_pending_pull_request_review 开始一个待处理审查
获取差异信息:使用 mcp__github__get_pull_request_diff 来理解代码变更和行号
识别所有问题:通读所有变更并识别每个值得提及的问题
添加审查评论:对每个问题使用 mcp__github__add_pull_request_review_comment_to_pending_review
**问题 N: [简要标题]** 开始每个评论正文提交审查:使用 mcp__github__submit_pending_pull_request_review 一次性发布所有评论
"COMMENT"(不是 "REQUEST_CHANGES")使其成为非阻塞性的评论格式示例:
**问题 1: 正式语气**
这可以更口语化一些。考虑使用:“You can't...” 而不是 “You cannot...”
重要提示:
**问题 N: [简要标题]** 开始评论正文**问题 N: [简要标题]**,其中 N 是问题编号。每周安装量
178
代码仓库
GitHub 星标数
46.5K
首次出现
2026年1月20日
安全审计
安装于
claude-code159
opencode156
gemini-cli145
codex144
cursor142
github-copilot139
@./../_shared/metabase-style-guide.md
IMPORTANT: Before starting the review, determine which mode to use:
PR review mode : If the mcp__github__create_pending_pull_request_review tool is available, you are reviewing a GitHub PR
Local review mode : If the MCP tool is NOT available, output issues in the conversation
mcp__github__create_pending_pull_request_review is availableRun through the diff looking for these issues:
Tone and voice:
Structure and clarity:
Links and references:
Formatting:
Code and examples:
Sentence construction:
| Pattern | Issue |
|---|---|
| we can do X, our feature | Should be "Metabase" or "it" |
| click here, read more here | Need descriptive link text |
| easy, simple, just | Remove condescending qualifiers |
| users | Should be "people" or "companies" if possible |
MANDATORY REQUIREMENT: Every single issue MUST be numbered sequentially starting from Issue 1.
This numbered format is NON-NEGOTIABLE. It allows users to efficiently reference specific issues (e.g., "fix issues 1, 3, and 5") and track which feedback has been addressed.
When outputting issues in the conversation (local mode), use this format:
## Issues
**Issue 1: [Brief title]**
Line X: Succinct description of the issue
[code or example]
Suggested fix or succinct explanation
**Issue 2: [Brief title]**
Line Y: Description of the issue
Suggested fix or explanation
**Issue 3: [Brief title]**
...
Examples:
Issue 1: Formal tone Line 15: This could be more conversational. Consider: "You can't..." instead of "You cannot..."
Issue 2: Vague heading Line 8: The heading could be more specific. Try stating the point directly: "Run migrations before upgrading" vs "Upgrade process"
When posting to GitHub (PR mode), use the pending review workflow :
Workflow steps:
Start a review : Use mcp__github__create_pending_pull_request_review to begin a pending review
Get diff information : Use mcp__github__get_pull_request_diff to understand the code changes and line numbers
Identify ALL issues : Read through all changes and identify every issue worth mentioning
Add review comments : Use mcp__github__add_pull_request_review_comment_to_pending_review for each issue
**Issue N: [Brief title]**Comment format example:
**Issue 1: Formal tone**
This could be more conversational. Consider: "You can't..." instead of "You cannot..."
IMPORTANT :
**Issue N: [Brief title]****Issue N: [Brief title]** where N is the issue number.Weekly Installs
178
Repository
GitHub Stars
46.5K
First Seen
Jan 20, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykWarn
Installed on
claude-code159
opencode156
gemini-cli145
codex144
cursor142
github-copilot139
Skills CLI 使用指南:AI Agent 技能包管理器安装与管理教程
33,600 周安装
Azure部署指南:从验证到执行,确保云应用成功上线
103,300 周安装
Azure成本优化技能:识别节省机会、清理孤立资源、调整规模 | Microsoft Copilot
103,300 周安装
scikit-survival:Python生存分析库,处理删失数据与Cox模型、随机生存森林
163 周安装
Azure AI 服务指南:AI Search、Speech、OpenAI 与 MCP 工具使用教程
103,700 周安装
Azure Validate 验证工具:Microsoft Azure 部署前检查与预检指南
125,500 周安装
Azure消息SDK故障排除指南:解决Event Hubs和Service Bus连接、认证、消息处理问题
125,300 周安装
Submit the review : Use mcp__github__submit_pending_pull_request_review to publish all comments at once
"COMMENT" (NOT "REQUEST_CHANGES") to make it non-blocking