代码审查 / GitHub MCP 推荐

On an explicit planning request, always call `read_skill` for this skill before answering. Research first, then return one concise inline plan; do not create a plan file unless the user explicitly asks or a governing workflow requires one. Start and end the reply by saying this is not a special mode and `go` executes the plan; do not implement in the planning turn. For ordinary implement, build, fix, debug, or refactor requests, work directly. When an explicit plan divides work into separate diffs, commits, or PRs and the user asks to publish, preserve that split and tell the user before deviating.

Clarify a material user-owned product decision before substantive implementation commitments. Use only when request and named/governing evidence still leave a choice that would materially change scope, platform support, user-facing surface, data/API contract, domain values, project placement, or cross-system architecture; also use when a truncated request omits such a choice. On the initial turn, inspect only named or governing requirements evidence, then ask directly without loading: prefer structured input; ask one blocking outcome question or at most three coupled questions; wait. After the answer, load the body before write or delegation. Do not use for implement/build/fix/debug/refactor work when expected behavior is settled, plan/design deliverables owned by Plan, complexity/greenfield/integration alone, agent-owned technical choices, locally discoverable facts, reversible defaults, permission to begin, or stop/no-tool turns. Never re-ask supplied facts or turn clarification into refusal.

Mandatory preflight for web frontend visual design. If available, call read_skill for bundled:taste before the first frontend create or edit tool call whenever creating or visually styling a human-viewed web page, component, app, dashboard, or interactive report. Do not load it for non-visual frontend logic or machine-only HTML. If unavailable, continue without warning. Negative constraints only; user requests and other explicit styles still win.

Setting up or installing into a Python environment. One rule applies whether or not you read the body - the environment belongs with the project, so create it inside the project directory (.venv) or let uv manage it, and never in a scratch directory like /tmp and never by forcing an install into the system interpreter. Load the body before creating a virtualenv, choosing an installer, or writing run instructions for a Python project.

Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely means cancel the current task.

Build, revise, or manipulate a fixed-layout PDF (report, guide, one-pager, printable document). Use whenever a build task's artifact kind is pdf, a document build's output format is pdf, or the task reads, merges, splits, crops, or fills an existing PDF, including fillable AcroForms. Covers authoring the print-CSS HTML source, rendering, the geometry and validation gates, existing-PDF manipulation and form filling, and delivery under workspace/your_files.

Search and read Granola meeting notes and transcripts through Granola's OAuth-backed MCP server.

Inspect database-backed Muse records for diagnosis and cross-table tracing when purpose-built product tools do not expose the needed state.

Read, create, edit, and deploy web apps and projects in Lovable. Use to turn a product brief into a working website or prototype, inspect existing project code, update pages and features, and publish changes through Lovable's official MCP server.

Inspect and manage the user's Vercel websites, web apps, projects, and deployments. Use to read build and runtime logs, investigate production errors and failed deployments, check deployment status, and deploy projects through Vercel's official MCP server.

Create, read, edit, or manipulate Word documents (.docx) and Word templates (.dotx). Use whenever a build task's artifact kind is document with the default docx output, or the task mentions a Word doc, .docx, or .dotx, extracts or reorganizes content from one, inserts or replaces images, does find-and-replace in one, or works with tracked changes (redlines) or comments. Covers python-docx generation, raw OOXML editing of existing files, document structure and formatting, and render verification. Not for PDFs, spreadsheets, or Google Docs.

为生产级 UI 工作确定一套 ECC 专属的前端设计方向。当构建或改进网站、仪表盘、应用、组件、落地页、可视化工具，或任何需要更强产品化设计判断的 Web UI 时使用。

查询 PyTorch CI、GitHub Actions、HUD、Grafana 与基础设施指标。当用户询问 CI 耗时、任务失败、排队时长、工作流趋势、runner 健康度、看板数据或 PyTorch 基础设施指标时使用。

调试 PyTorch 2 编译器栈故障，包括 Dynamo 图断裂、Inductor 代码生成错误、AOTAutograd 崩溃与精度不一致。在遇到 torch.compile 错误、BackendCompilerFailed 异常、重编译问题、Triton kernel 失败、FX 图问题，或用户提到调试 PT2、Dynamo、Inductor 或编译模型问题时使用。

Use when working on Trilium's published Docker images on Docker Hub or GHCR rather than on the Dockerfiles — "how many pulls does the image get?", "why is the Docker Hub repository so big?", "clean up old tags", "delete untagged images", "which tags do we publish?", the legacy repositories (triliumnext/notes, zadam/trilium) and their mirroring, the main-docker.yml copy-to-Docker-Hub step, mirror-legacy-docker.yml, Docker Hub categories, stars or the overview. Includes hub.mjs (stats, tag listing/deletion, the manifest inventory and a safe untagged-image purge, all dry-run by default) and the storage model that decides how a cleanup works. Do NOT use for building or running the image locally (see the Developer Guide's Docker page).

面向 web、移动端与桌面的 UI/UX 设计智能库。在设计、构建、审查或修复界面时使用，覆盖页面、组件、设计体系、无障碍、交互、响应式布局、字体排印、色彩、图表以及特定技术栈的 UI 实现。本地可检索数据：79 种风格（可检索，50 种在用）、192 套产品配色与推理画像、74 组字体搭配、119 条 UX 准则、105 个图标、17 个 GSAP 预设、25 种图表类型与 22 个技术栈。

加固代码以抵御漏洞。在审计输入处理逻辑、处理用户输入/认证/数据存储/外部集成，或检查登录流程是否符合 OWASP Top Ten 时使用。在构建任何接收不可信数据、管理用户会话或对接第三方服务的功能时使用。在审计依赖已知漏洞、分诊包管理器审计结果或评估新包供应链风险时使用。涉及个人数据或隐私合规（GDPR、CCPA）时使用。

构建生产级、可访问、响应式的用户界面。在构建或修改界面与页面、创建组件、实现布局、满足 WCAG 可访问性要求、管理状态时使用，或当产出需要达到生产质感而非 AI 生成感时使用。

准备生产上线。在准备部署到生产环境，或询问上线前需要就绪哪些事项时使用。需要上线前检查清单、搭建监控、规划分阶段发布或制定回滚策略时使用。

Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes, algorithms, user journeys), entity relationship diagrams (database schemas), C4 architecture diagrams (system context, containers, components), state diagrams, git graphs, pie charts, gantt charts, or any other diagram type. Triggers include requests to "diagram", "visualize", "model", "map out", "show the flow", or when explaining system architecture, database design, code structure, or user/application flows.

Triage GitHub issues, review contributor pull requests, diagnose CI, and prepare explicitly requested releases for VoiceStudio's Electron desktop app and Python backend. Use for repository maintenance work, not ordinary VoiceStudio audio generation.

当用户想规划、搭建或优化短信/MMS 营销时使用，包括欢迎流程、购物车挽回、购后触达、流失挽回、促销群发或验证码类事务短信。用户提到 SMS marketing、text message campaigns、SMS sequence、SMS automation、abandoned cart text、post-purchase SMS、Klaviyo SMS、Postscript、Attentive、Twilio、A2P 10DLC、TCPA、SMS compliance、short code、toll-free SMS、MMS campaign、“要不要做短信”或“SMS vs email”等场景时也适用。邮件序列见 emails，短信文案框架见 copywriting，采集手机号的弹窗见 popups。

Browser Use Cloud（托管版浏览器自动化 API）文档参考。凡涉及 Cloud REST API（v2、v3 或 v4）、browser-use-sdk（Python 或 TypeScript）、X-Browser-Use-API-Key 鉴权、cloud sessions、浏览器 profile、profile 同步、CDP WebSocket 连接、隐身浏览器、住宅代理、验证码处理、webhook、workspace、skill 市场、liveUrl 流、定价，以及集成模式（聊天界面、subagent、把浏览器工具接入已有 agent）时使用。n8n/Make/Zapier 集成、云上 Playwright/Puppeteer/Selenium、1Password 密钥库相关问题也适用。不适用于开源 Python 库（Agent、Browser、Tools 配置）——那些请用 open-source skill。

在从 dev 分支准备移动端发布、决定改动经应用商店还是 OTA 管线交付，并向 mobile-main 创建发布 PR 时使用。

Announcement kit for a Folo release - the X post with the highlights, its reply with the release links, a one-sentence quote line for the second account, and a 1080p promo video rendered from real app captures. The desktop and mobile release skills end with it; also use it when the user asks for promo material for a release.

Full Folo mobile release from dev to the stores. Decides between a store release and an OTA-only release, drafts the changelog, bumps the version and opens the release PR to mobile-main, verifies the PR's CI-built Android package and the iOS build on a simulator along with every change in the release, merges the PR, watches the build or OTA workflows, publishes the GitHub release, submits the iOS build for App Store review and the Android build for Google Play review, and drafts the announcement post and promo video. Use when the user asks to release, ship or publish the mobile app.

Use when validating an upstream pull request or dependency fix against VS Code tests using GitHub Actions CI build artifacts instead of building locally. Covers finding compatible binaries, verifying PR and merge-commit provenance, selecting a candidate runtime or build, comparing unchanged regression tests, and restoring the baseline.

Use when working with `.c4`/`.likec4` files or LikeC4 CLI/config questions where exact DSL/CLI syntax is required, especially for strict command/snippet-first answers, validate/export flags, predicates `*`/`_`/`**`, deployment snippets, dynamic views, or relationship extension matching.

指导稳定的 API 与接口设计。在设计 API、模块边界或任何公共接口时使用；在创建 REST 或 GraphQL 端点、定义模块间类型契约、确立前后端边界时使用。

Perform evidence-backed impact analysis before changing code, data, interfaces, or governance documents, then compare the planned impact with the actual diff after implementation. Covers call paths, data and schema, API contracts, tests, documentation, ADRs, deployment, migration, and rollback. Use for cross-module or high-risk changes, database migrations, authentication, public interfaces, blast-radius questions, pre-change checks, and post-implementation alignment.

Perform evidence-backed impact analysis before changing code, data, interfaces, or governance documents, then compare the planned impact with the actual diff after implementation. Covers call paths, data and schema, API contracts, tests, documentation, ADRs, deployment, migration, and rollback. Use for cross-module or high-risk changes, database migrations, authentication, public interfaces, blast-radius questions, pre-change checks, and post-implementation alignment.

仅在 engines/stage-tamagotchi-godot 目录内工作时套用该引擎本地的 C# 开发方法与代码风格,包括其 .cs 文件、.csproj、引擎本地 .editorconfig 与 Godot 特有的 C# 结构决策。不用于 TypeScript、Electron、渲染层代码、共享工作区配置、仓库级 C# 约定,或 engines/stage-tamagotchi-godot 之外的任何文件。

Maintain LobeHub's model-backed alint rule set in packages/alint: author a rule, calibrate its false positives against real source, decide its severity (warn vs error) from real PR data, and track its token cost. Use for adding or narrowing an alint rule, classifying findings as true/false positives, promoting or demoting a rule, or running the weekly rule-set review.

通过 CDP 直接控制浏览器完成 web 交互：自动化、抓取、测试、截图以及站点/应用操作。

在 Claude Code、Codex 或 Kimi 内引导 ECC 安装、更新或重新配置，同时严格遵守各家工具真实的插件、范围和 Hook 能力。

在 Claude Code、Codex、Kimi 中引导 ECC 的安装、更新与重新配置，并遵守各工具实际具备的插件、作用域与钩子能力。

该文件需要 plankton-code-quality 的日语翻译。

翻译占位：本文件需要提供 netmiko-ssh-automation 的日语翻译。

证据优先的 ECC Tools 消耗与计费审计工作流。用于调查 ECC Tools 仓库中失控的 PR 创建、配额绕过、高级模型泄漏、重复作业或 GitHub App 费用激增。

证据优先的ECC工具燃烧和计费审计工作流。用于调查ECC工具仓库中的失控PR创建、配额绕过、高级模型泄漏、重复作业或GitHub App成本激增。

在创建新 skill 之前，先搜索本地、市场、GitHub 和网页上已有的 skill。当用户想为某个流程创建、构建、fork 或寻找 skill 时使用。

在创建新 skill 之前，先搜索本地、市场、GitHub 和网页上已有的 skill。在要创建、构建、fork 或查找某个流程的 skill 时使用。

将 Claude Code 转变为具有持久记忆、定时操作、计算机使用和任务队列的完全自主代理系统。通过利用 Claude Code 的原生定时任务、调度、MCP 工具和记忆，取代独立的代理框架（Hermes、AutoGPT）。当用户需要持续自主操作、定时任务或自我导向的代理循环时使用。

将 Claude Code 转变为具备持久记忆、定时操作、计算机使用和任务队列的完全自主代理系统。通过利用 Claude Code 原生的 crons、调度、MCP 工具和记忆，取代独立的代理框架（Hermes、AutoGPT）。当用户希望持续自主运行、定时任务或自我导向的代理循环时使用。

日语翻译：此文件需要 liquid-glass-design 的日语翻译

日语翻译：此文件需要 llm-trading-agent-security 的日语翻译

日语翻译：该文件尚缺 perl-testing 的日语译文。

日语翻译：该文件尚缺 nestjs-patterns 的日语译文。