菜单
Review the current branch's changes (or a specific PR). Use when the user asks to "review my branch", "review this", "review PR <number>", or "/mochi-review [number]". Always consumes the entire diff into context, then produces a thorough, concise code review.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use whenever the user asks to build, add, or modify anything in this Mochi app — pages, routes, islands, selective/lazy/server hydration, forms, JSON/WS/SSE endpoints, cookies, caching, or request context. Before writing any framework code, invoke the "mochi" skill to fetch the relevant Mochi docs and demos.
Add a new lifecycle event to Mochi's event bus (`packages/mochi/src/events.ts`). Use when the user asks to "add an event", "emit a new event", "create a new mochiEvents emission", or "/add-event <name>". Walks the payload type, the `MochiEventMap` registry, the emission site, public exports, optional logger wiring, tests, and docs.
Mutation-test unit tests to verify they catch real failures. For each test, temporarily breaks the source code it exercises, confirms the test fails, then reverts. Flags mock-only tests and suggests fixes. Use when the user says "validate tests", "test-validator", or wants to check test quality.
Take a 16:9 screenshot of a single component via the /shot/:name endpoint (`packages/site/src/shot/`). Use when the user asks to "screenshot a component", "take a component screenshot", "generate an image of <component>", "grab a shot of X for the docs", or "/component-screenshot <component>". Covers registering a new subject, sizing, and driving the browser.
Stage and commit the current working changes with a short release-please-style commit title. Does not push. Use when the user says "commit", "commit my changes", or "/commit". Optional args list paths to skip (e.g. "/commit ignore IMPROVEMENTS.md").
Add a new hook or filter to Mochi's extension API (`packages/mochi/src/extensions.ts`). Use when the user asks to "add a hook", "add a filter", "create an extension point", or "/add-extension <name>". Walks both halves of the type/runtime kind-map registry and the call-site wiring.
| name | mochi-review |
| description | Review the current branch's changes (or a specific PR). Use when the user asks to "review my branch", "review this", "review PR <number>", or "/mochi-review [number]". Always consumes the entire diff into context, then produces a thorough, concise code review. |
You are an expert code reviewer. Follow these steps:
Determine the target:
gh pr view <number> --json title,body,author,baseRefName,headRefName,state,additions,deletions,changedFiles,labels for details.git rev-parse --abbrev-ref HEAD to confirm the branch, and git log --oneline main..HEAD (or against the appropriate base) plus git diff --stat main...HEAD to understand its scope.Read the entire diff:
gh pr diff <number>.git diff main...HEAD (use the actual base branch if not main).git diff main...HEAD -- <path>, or use --stat to enumerate files and then fetch each one) until 100% of the changes have been read. Do not sample, skim, or summarize files you have not actually loaded.Analyze the changes and provide a thorough code review that includes:
Keep your review concise but thorough. Focus on:
Format your review with clear sections and bullet points.
Target (PR number or empty for current branch): $ARGUMENTS