Create Commit Message

Overview

Generate a precise, Conventional Commits-formatted commit message by analyzing the staged git diff. The message classifies the change type, infers the scope from changed files, writes a clear subject line under 72 characters, and adds a body for complex changes explaining why the change was made.

Workflow

1. Read project context -- Check for .chalk/docs/engineering/ files, especially:

   • Commit message conventions or contributing guides
   • Any custom commit types or scopes used by this project
   • Check for a commitlint.config.js or similar configuration that defines allowed types and scopes
   • If custom conventions exist, follow those instead of the defaults below

2. Get the staged diff -- Run:

   • git diff --cached --stat for a high-level overview of changed files
   • git diff --cached for the full diff content
   • git status to check for unstaged changes the user may have forgotten to stage
   • If nothing is staged, inform the user and suggest staging commands