x-commit

To generate a git commit message from a diff, the Skill analyzes your staged changes or working tree to draft a formatted type and subject message with an English body. It uses cached diffs if staging exists, otherwise defaulting to the working tree.

Yes, you can run a local git commit without pushing, as the Skill enforces local-only execution with strict guardrails. It creates the commit directly on your machine without executing any push commands to the remote repository.

Yes, the commit workflow supports pre-commit hooks by enforcing safety constraints that prevent skipping verification. It explicitly avoids broad git add commands like git add -A, ensuring only specific diff-scoped changes are staged and validated.

The correct format for a local commit message requires a specific type prefix followed by an English subject and a detailed body. The Skill enforces this strict formatting based on the analyzed diff content to ensure deterministic local results.

To manually trigger a local commit for your current changes, you must explicitly request the action using a command like /commit or a direct instruction such as "commit my changes". The Skill operates exclusively on explicit user request.

No, broad git add commands like git add -A or git add . are not allowed when staging files for a commit. The Skill applies diff-scoped staging rules to add only the relevant changes, preventing accidental inclusion of unrelated files.