commit-messagelisted

# Commit Message Suggester Generate a conventional commit message by analyzing all local git changes (staged, unstaged, and untracked) without performing any commit. ## Workflow ### 1. Gather Change Context Read `$CLAUDE_PLUGIN_ROOT/skills/commit/references/gather-changes.md` and follow the procedure (multi-repo detection + git commands). ### 2. Analyze Changes and Generate Conventional Commit Message 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. ### 3. Present the 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. ## Important - Never commit, stage, or modify any files - This skill is read-only — it only analyzes and suggests - When changes are too broad for a single commit, recommend splitting Recommend the next step based on readiness: - If the user wants to commit now → `/optimus:commit` to commit (and optionally push) - If the feature