メニュー
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").
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
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.
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.
Check whether the scripts vendored under packages/mochi/src/vendor/ are on the latest upstream release, and update the ones that aren't. Use when the user asks to "check vendored versions", "update vendored scripts", "refresh vendored deps", or "/update-vendored".
SOC 職業分類に基づく
| name | commit |
| description | 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"). |
| user-invocable | true |
| model | sonnet |
Stage everything in the working tree (modified + untracked) and create one commit with a short Conventional Commits title.
🤖 Generated with Claude Code, no Co-Authored-By: Claude (or similar) trailers — not in commit messages and not in PR bodies. Claude Code's attribution setting governs this; never add it by hand. Same for any "generated by"/AI-tool credit.feat:, fix:, perf:, chore:, docs:, refactor:, test:, ci:, build:. Use feat!: only if the user explicitly says it's a breaking change..env*, credentials*, key files)..devcontainer/devcontainer.json — leave its changes uncommitted in the working tree.git status and git diff (and git diff --staged) in parallel to see what would be committed.git add <path> ... — do NOT use git add -A or git add .. Exclude any paths the user told you to ignore.git commit -m "<title>" — one -m, no second -m, no heredoc body.If you are asked to additionally create a PR, write a PR title in release-please style. Write a very short, bullet-point description — and, per the rule above, no attribution / "Generated with Claude Code" footer in the body.