メニュー
Commit current work by reviewing diffs, splitting into logical commits, and writing standardized messages. Use when the user says "commit", "commit this", "commit current work", or asks to create a git commit.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Scan recent changes for AI-generated code slop and remove it. Use when the user says "deslop", "remove slop", "clean up AI code", or asks to remove AI-generated artifacts from the codebase.
Resolve all merge conflicts on the current branch non-interactively, validate the build, and commit. Use when the user says "fix merge conflicts", "resolve conflicts", or when git status shows conflicting files.
Orchestrates implementation of a multi-task plan by spawning plan-implementer subagents in parallel. Use when the user provides a plan file or plan text and asks to implement it, execute it, or says "implement plan", "run plan", "execute plan".
Resolve on-screen seedit DOM elements to React source files, line numbers, component names, and ownership stacks using the app's dev-only element-source helpers and playwright-cli. Use when an agent needs to inspect a page element, map a snapshot ref to source code, confirm which component rendered a node, or follow up after $profile-browsing finds a rerender hotspot and needs file-level attribution.
Profile app performance while browsing, collecting Web Vitals and React rerender data via react-scan. Orchestrates parallel profiler subagents via playwright-cli to capture navigation timing, long tasks, layout shifts, LCP, React commit counts, render bursts, and per-component render data. Use when profiling browsing performance, finding bottlenecks, diagnosing excessive rerenders, or auditing page performance.
When the user wants to create or update a README.md file for a project. Also use when the user says "write readme," "create readme," "document this project," "project documentation," or asks for help with README.md. Produces thorough, verified documentation covering local setup, architecture, and distribution.
| name | commit |
| description | Commit current work by reviewing diffs, splitting into logical commits, and writing standardized messages. Use when the user says "commit", "commit this", "commit current work", or asks to create a git commit. |
| disable-model-invocation | true |
Review all uncommitted changes
git status
git diff
git diff --cached
Read every changed file's diff to understand the full scope of changes.
Group changes into logical commits
If diffs are unrelated, split into multiple commits. Each commit should cover one logical unit of work.
Example — two unrelated changes in the working tree:
src/components/reply-modal.tsx (UI fix)src/stores/use-settings-store.ts (new setting)These should be two separate commits, not one.
Stage and commit each group
For each logical group:
git add <relevant files>
git commit -m "title here"
Display the commit title to the user wrapped in backticks (inline code).
Title format: Conventional Commits with a required scope. The scope should be a short, human-readable name for the area of the codebase affected.
| Pattern | Example |
|---|---|
type(scope): description | feat(reply modal): add textarea |
Never omit the scope. feat: add textarea is wrong. feat(reply modal): add textarea is correct.
Keep titles short. If more context is needed, add a commit body — but don't repeat the title.
Use perf: for performance optimizations, not fix:.