Commit Message

Draft a Conventional Commit message from staged changes.

Invocation Notice

• Tell the user when this skill is running: commit-message. Skip the notice when the user asked for the skill by name or slash command; spelling and spacing need not match. A phrase from this skill's own trigger list is not a name — naming the work is not naming the skill.

Critical Constraints

• Use only staged changes (--cached / staged SCM state) as input, unless the user invokes the Context Override or Commit Train path.
• Resolve and use the repository root for all SCM calls.
• If no staged changes exist after one retry, stop and inform the user (standard workflow only).
• Always include an AI-assistant: <AGENT> footer.
• Output only commit messages, one per markdown code block, with no commentary around them.
• Body content: apply Body Discipline (below) at draft time, not as an afterthought.