From optimus
Suggests conventional commit messages by analyzing staged, unstaged, and untracked git changes — read-only, never commits.
How this skill is triggered — by the user, by Claude, or both
Slash command
/optimus:commit-messageThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate a conventional commit message by analyzing all local git changes (staged, unstaged, and untracked) without performing any commit.
Generate a conventional commit message by analyzing all local git changes (staged, unstaged, and untracked) without performing any commit.
Read $CLAUDE_PLUGIN_ROOT/skills/commit/references/gather-changes.md and follow the procedure (multi-repo detection + git commands).
Read $CLAUDE_PLUGIN_ROOT/skills/commit-message/references/conventional-commit-format.md and follow its instructions to analyze the gathered changes and generate a conventional commit message.
Output the suggested commit message in a copyable code block. Do NOT run git commit. If the changes naturally split into multiple commits, present each message separately with instructions on which files to stage for each.
In a multi-repo workspace, present each repo's commit message under a heading with the repo directory name (e.g., ## isa-server). If a repo's changes span multiple concerns, suggest separate commits within that repo's section. If only one repo has changes, still label it with the repo name for clarity.
Recommend the next step based on readiness:
/optimus:commit to commit (and optionally push)/optimus:pr to create a pull requestTell the user the closing tip per $CLAUDE_PLUGIN_ROOT/references/skill-handoff.md "Closing tip wording" — use Variant A with <continuation-skill(s)> = `/optimus:commit` or `/optimus:pr` and <non-continuation-examples> = /optimus:code-review, /optimus:unit-test, etc.
npx claudepluginhub oprogramadorreal/optimus-claude --plugin optimusGenerates conventional commit messages from staged changes by analyzing git diff and status. Helps users write structured, meaningful commits.
Generates conventional git commit messages from staged changes, unstaged diffs, and recent history. Uses git status, diff --cached, diff, log. Outputs type(scope): summary with body.
Generates clear, conventional commit messages from git diffs. Useful when writing commit messages, reviewing staged changes, or preparing commits.