commit

To generate a conventional commit message from your git diff, the skill reads your current changes, recent commit history, and branch context to compose a single atomic commit focused on the WHY. It stages appropriate files automatically while avoiding secrets.

Staging code changes without including .env files or secrets is handled automatically by reading the git status and diff to select relevant files. It avoids staging credentials and produces one safe, atomic commit for the working tree.

The best way to match a new commit message to your repository style is by reading recent commit history and branch context. The skill analyzes existing conventions to generate a conventional-commits message aligned with your project's established formatting.

Yes, you can append a Co-Authored-By trailer to an automatically generated conventional commit. You provide the desired trailer text as an argument, and the skill composes the final git commit message using a HEREDOC format that includes your specified details.

This tool creates exactly one atomic commit for your current working tree. It stages selected files from the diff and produces a single commit to encapsulate the changes, reducing the need for follow-up corrections.

An automated commit message generator reads your code changes and branch context to produce style-matched conventional commits. This prevents ambiguous messages and ensures your commit history explains the reasoning behind the changes rather than just the actions taken.