Generate Commit Message

Use this skill for requests that are specifically about reviewing staged changes and drafting a commit message for them.

Arguments

• [model name] (optional): Any arguments passed to the skill (e.g., /generate-commit-message Gemini Flash 3.8 (Medium)) specify the <model name> to be used in the commit message footer.

Workflow

1. Load the git-workflows skill and read its references/op_commit_message.md.
2. Follow that operation exactly, with these inputs:
   • Review: requested. Perform step 2 ("Review") inline, as the operation describes.
   • Footer: Use any provided argument as the <model name> in the commit message footer (Commit message generated by <harness name> (<model name>)) during step 4 ("Draft the commit message"). If no argument is provided, follow the default footer instructions.
3. Do not invent a parallel commit-message process in this skill. This skill exists to make the trigger explicit, request the review, forward any specified model name, and route the task into the canonical git workflow.

Trigger Examples

• /generate-commit-message Gemini Flash 3.8 (Medium)
• "Generate a commit message for the staged changes using Gemini Flash 3.8 (Medium)."
• "Generate a commit message for the staged changes."
• "Write a commit message for what I have staged."
• "Summarize the staged diff as a conventional commit."

Scope

This skill is only for staged changes. If nothing is staged, the operation's step 1 stops the process.