commit-staged

To generate a conventional commit message from staged changes, the skill analyzes your git diff --cached output to produce a structured commit plan with type, scope, and subject. It also incorporates session history and invocation context to document the rationale behind the modifications.

The best way to include extra context when crafting a git commit message is to provide that context during skill invocation. The skill uses this additional information to enrich the commit body with motivation, findings, and rationale alongside the generated conventional commit structure.

No, this commit message generator does not work with unstaged files in your version control workflow. It strictly analyzes only staged changes to ensure the generated commit message accurately reflects the exact modifications scheduled for the next commit snapshot.

To document the rationale for complex git commits in conventional format, the skill integrates motivation from available session history and applies provided invocation context. It enforces the conventional commit structure while adding detailed notes explaining why the changes were made.

Yes, you can use session history to enrich your git commit messages automatically. The skill integrates available session history to extract motivation and context, weaving this background information into the standardized commit notes and body text.