generate-commit

To generate git commit messages from diffs, the Skill reads actual git diff --cached and git diff outputs to produce standardized headers and bodies, ensuring descriptions match real repository changes. It enforces commit message rules and detects temporary files before committing.

The best way to split unrelated changes into atomic commits is using file-level or hunk-level split plans. The Skill analyzes git diff outputs, detects unrelated changes, and generates specific staging instructions using git add -p for precise hunk-level separation.

Yes, you can automatically execute file-level commit splitting. The Skill sequentially stages and commits files according to the generated split plan, handling the entire workflow automatically for file-level separations while providing instructions for hunk-level splits.

Temporary file detection during git staging works by scanning staged changes for typical transient files like .bak, .tmp, and CONTEXT.local.md. The Skill identifies these files and prompts whether they should be unstaged before generating the final commit message.

Commit messages should be generated from actual git diff output to avoid hallucinated changes based on conversation context. Reading real diff outputs guarantees that the subject and body descriptions match the staged or unstaged repository changes with complete accuracy.