メニュー
Stage all changes and create a conventional commit with a generated message. Use when ready to commit and want automated staging and commit message generation.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| title | safe-commit |
| name | safe-commit |
| description | Stage all changes and create a conventional commit with a generated message. Use when ready to commit and want automated staging and commit message generation. |
| disable-model-invocation | true |
| allowed-tools | Bash(git add *) Bash(git commit *) Bash(git diff *) Bash(git status *) |
Run:
git status
Show the output. If there is nothing to commit (working tree clean), stop and report that there are no changes to commit.
If there are staged changes, run:
git diff --staged
If there are no staged changes but there are unstaged changes, run:
git add -A
Then confirm: "Staged all changes. Run git diff --staged to review."
Run git diff --staged and show the output.
Analyze the staged diff and write a commit message following the Conventional Commits format:
<type>(<scope>): <short summary>
<body — optional, only if the why is not obvious from the diff>
Types: feat, fix, refactor, test, docs, chore, perf, style.
Rules:
Present the proposed commit message to the user before committing.
After presenting the message, run:
git commit -m "<generated message>"
If the commit fails (for example, a pre-commit hook rejects it), report the hook output verbatim and stop. Do not retry with a different message unless the user asks.
Show the result:
git status
Report the commit hash from the output of the commit command and confirm the working tree is clean.
Explains code in plain language for someone unfamiliar with the programming language. Use when asked to explain code, walk through logic, describe what a function does, or when the user says "explain this" or "walk me through this".
Summarizes uncommitted git changes in a concise machine-readable format. Use in CI pipelines, scripts, or headless invocations where the output will be piped or captured.
Explains what a skill is and demonstrates that skills are working. Use when testing skills, when asked about skills, or when asked to demonstrate how skills work.
Demonstrates the personal scope for Claude Code skills. Use when testing personal-scoped skills or when the user wants to understand the difference between personal and project skill scopes.
Lists the conventions for this project and demonstrates the project scope for Claude Code skills. Use when asked about project conventions, code style, or as a demonstration of project-scoped skills.
Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.