review-canvas
Present a multi-file code review as a Canvas diff artifact. Use when the user asks for a review, 代码评审, 变更审查, or a cross-file summary of changes — not for a single edit (the chat diff card already shows it) or a prose report (report-canvas).
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-13
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- review-canvas
- description
- Present a multi-file code review as a Canvas diff artifact. Use when the user asks for a review, 代码评审, 变更审查, or a cross-file summary of changes — not for a single edit (the chat diff card already shows it) or a prose report (report-canvas).
02 资源文件 1
- 参考文档ability.json921 B
03 SKILL.md 正文
Canvas code review
Write one conversation-owned artifact whose content is a Unified Diff, so the Canvas tab renders it file by file with per-file stats and folding.
When to use
Use this Skill when the change spans several files and the user needs to review it as a whole: 完成一个任务后的验收、一段重构后的对照、准备提交前的自查。Single-file edits already render as a diff card in chat — do not duplicate them here.
Contract
contentType: "text/x-diff",content就是标准 Unified Diff 文本(可以含多个diff --git段)。- 或者用
kind: "code-change",渲染层按同一分支处理。 - 每个文件分段以
diff --git a/<path> b/<path>开头,后面跟---/+++/@@头与增删行。 - 不要用 Markdown 表格或自定义 JSON 描述差异;解析与染色走与聊天里同一套 diff 渲染。
Workflow
- 先把真实差异取出来(
git diff、工具结果里的 diff,或edit_file/write_to_file的details.diff), 不要凭记忆重写差异文本 —— 行级内容对不上就失去了审查价值。 artifactcreate,kind: "code-change",contentType: "text/x-diff",title写清审查对象 (例如「PR #12 变更」),content放完整 Unified Diff。- 用户要求追加新变更时走
artifactupdate+baseVersion,保持同一份 artifact 的版本历史。 - 聊天里给出结论(风险点、需要重点看的文件),不要重贴整份 diff。
Failure modes
- diff 被截断或缺少
diff --git头时,画布会按单个文件渲染或降级为代码视图;这时补全 diff 再update。 - 只改了文件的一部分时,明确写出范围(哪个文件、哪些 hunk),不要让读者以为这是全量变更。
04 同仓库更多 Skills
report-canvas
Produce a standalone report, audit board, or long-form analysis as a Canvas artifact. Use when the user asks for a report, 报告, 审计看板, or a deliverable that should live beside chat — not when they only want a short chat answer or to inspect a live web page.
publish-ability
Publish a skill, scene, MCP server, plugin, or bundle to the Vetta ability marketplace. Use when the user asks to upload/publish/submit an ability, put a plugin on the marketplace, share a skill with other users, or migrate an existing package into Vetta.
install-ability
在本机 Vetta 中安装能力——插件(plugin)、Skill/场景(scene)与 MCP 服务器。用户说「装一个插件 / install plugin / 从能力市场安装 / 加一个 MCP server / 配置 MCP / 装个 skill」,或插件装完没生效、需要 reload、pending 版本没应用时使用。不用于安装 npm 依赖、IDE 插件、浏览器扩展,也不用于开发插件(那是 plugin-workbench)或创作 Skill(那是 create-skill)。
database-analysis
Answer business questions from connected databases with read-only queries, then analyze metrics, trends, rankings, breakdowns, and period comparisons. Use for 问数、查数、数据库分析、销量/收入/用户指标、同比环比 or follow-up data questions. Not for application database migrations or modifying records.
create-skill
Create or update Vetta-compatible Agent Skills. Use when the user asks to create a skill, add a SKILL.md workflow, register a skill in skills-manifest.json, package a skill in a Vetta plugin, or add a built-in Vetta skill preset.
chart-canvas
Render a trend or comparison chart as a Canvas artifact using the declarative chart contract. Use when the user asks for a chart, 趋势图, 折线图, 柱状图, 饼图, 占比, or a visual comparison of numbers — not for prose reports (report-canvas) or module diagrams (architecture-canvas).