Menu
Commit changes with proper formatting, changelog update, and checks. Use when the user wants to commit, save progress, or record changes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | commit |
| description | Commit changes with proper formatting, changelog update, and checks. Use when the user wants to commit, save progress, or record changes. |
| disable-model-invocation | true |
| argument-hint | ["commit message"] |
Commit changes following the project's conventions.
git fetch origin
git log --oneline origin/main ^main -5
If there are upstream commits not yet in local main, STOP and ask the user how to proceed.
Run git status and git diff to understand what's being committed. Summarize the changes for the user.
Read CHANGELOG.md and add entries under ## [Unreleased] describing the changes. Use the appropriate subsection:
Keep entries concise (one line each). Do not add empty subsections.
cargo fmt --all
just check
This runs build, license checks, format checks, and all tests. If anything fails, stop and fix before continuing.
Stage all relevant files (including CHANGELOG.md) and commit. If a message was provided as $ARGUMENTS, use that. Otherwise, draft a concise commit message based on the changes and confirm with the user.
Do not stage files that likely contain secrets (.env, credentials, etc.).