Generate Conventional Commits messages with enforced subject structure.
npx skills add https://github.com/mitsuhiko/agent-stuff --skill commit-mitsuhiko
Please help me install this Agent Skill. Skill: commit Source: https://github.com/mitsuhiko/agent-stuff/tree/main/skills/commit Command: npx skills add https://github.com/mitsuhiko/agent-stuff --skill commit-mitsuhiko
This Skill helps teams maintain a clean, navigable git history by generating standardized commit messages in the Conventional Commits style.
Stage your changes and run the commit tool to produce a Conventional Commits-style subject for the current changes.
High-intent search queries and answers about installing and using this skill.
To generate conventional commit messages, stage your changes and run the commit tool to produce a standardized subject formatted as <type>(<scope>): <summary> based on the current code changes.
A conventional commit subject line follows the structure <type>(<scope>): <summary>. The tool suggests the appropriate scope and type based on your specific changes and project conventions.
Yes, you can include an optional body in your conventional commit message to describe the rationale and impact of the code changes alongside the generated subject line.
No, you should avoid signing off commits. The tool guides users to review staged changes and generates the commit message without adding a sign-off.
The best way to maintain a clean git history is to apply this tool during development workflows to create standardized conventional commits for small incremental changes, features, fixes, and docs.
billwanggithubGenerate descriptive git commit messages from staged changes.
iludeValidate Git commits for secrets and enforce safe push rules.
aztr0nutzsCommit and push local workspace changes to a remote GitHub repository.
AmidVoshakulAutomate Git hook configuration for linting, formatting, and commit message validation.
