ワンクリックで
commit-helper
Generates clear commit messages from git diffs. Use when writing commit messages or reviewing staged changes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Generates clear commit messages from git diffs. Use when writing commit messages or reviewing staged changes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Build full-stack React applications with TanStack Start. Use when creating, configuring, or working with TanStack Start projects, routing, server functions, middleware, deployment, or when the user mentions tanstack/start.
Manage tasks, bugs, and features with the beans issue tracker. Use when creating, listing, updating, or working on beans, or when the user asks what to work on next.
Operational patterns for Cloudflare Wrangler CLI. Use when deploying workers, running D1 migrations, querying D1 databases, managing R2 buckets, or generating binding types. Distinct from cloudflare-api which covers documentation lookups.
Query Obsidian vaults via obi CLI. Use for any vault data lookup instead of grep or find -- searching notes, filtering by frontmatter (read status, type, tags), listing folders, reading sections, checking backlinks, and finding unread or recent notes.
Manage changelogs and versioning using the changesets CLI. Use when creating changesets, bumping versions, consuming changesets for a release, or maintaining CHANGELOG.md files.
Interact with tmux sessions, windows, and panes. Use when the user mentions tmux, dev servers, checking logs in panes, restarting services, or running commands in background terminals. Also covers tmuxinator for session management.
| name | commit-helper |
| description | Generates clear commit messages from git diffs. Use when writing commit messages or reviewing staged changes. |
| allowed-tools | Read, Bash(git:*) |
Generate commit messages following the Conventional Commits specification.
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Use ! after type/scope or add BREAKING CHANGE: footer:
feat!: redesign API response format
BREAKING CHANGE: Response format changed from array to object
docs: fix typo in README
feat(cli): add status command
fix: prevent race condition in request handling
- Introduce request ID tracking to dismiss stale responses.
- Remove obsolete timeout-based mitigation.
feat(api)!: change authentication flow
BREAKING CHANGE: JWT tokens now required for all endpoints
git diff --staged to see staged changes.Refs: #123)IMPORTANT: Be concise. Grammar does not matter as long as it's clear and concise. Try to keep the body within 2-3 bullet points with very concise sentences.