write-commit

To generate a conventional commit message from staged changes, run the skill against your active Git repository and provide a Card ID. It analyzes the staged diff to infer the commit type, scope, and detailed change list.

Commit message generation requires a Card ID to ensure traceability between your staged changes and work items. The skill blocks message creation unless you supply a valid CARD: #id, enforcing issue linking and preventing untraceable commits.

Conventional commit type inference works by analyzing the files currently staged in your Git repository. It evaluates the staged diff to suggest the appropriate commit type, such as feat, fix, or refactor, along with a helpful scope.

You cannot use this to generate commit messages for sensitive config files. The skill includes safety guardrails that prevent committing or handling sensitive configuration files during the staged diff analysis and message generation process.

The best way to structure a commit message from a Git staged diff is using a brief subject line followed by a bullet list of meaningful changes. The skill omits trivial formatting-only edits to maintain a clean, conventional commit structure.

This commit message generator does not work with multi-type staged changes. It is designed for scenarios where a single commit type can be inferred from the staged diff, ensuring accurate conventional commits for focused changes.