From optimus
Suggests conventional commit messages by analyzing staged, unstaged, and untracked git changes in single or multi-repo workspaces. Read-only; never commits or modifies files. Use when needing commit message ideas before committing.
npx claudepluginhub oprogramadorreal/optimus-claude --plugin optimusThis skill uses the workspace's default tool permissions.
Generate a conventional commit message by analyzing all local git changes (staged, unstaged, and untracked) without performing any commit.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.
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: Tip: for best results, start a fresh conversation for the next skill — each skill gathers its own context from scratch.