Create git commits in Conventional Commits format with descriptive bodies.
npx skills add https://github.com/v36372/pi-stuff --skill commit-v36372
Please help me install this Agent Skill. Skill: commit Source: https://github.com/v36372/pi-stuff/tree/main/skills/commit Command: npx skills add https://github.com/v36372/pi-stuff --skill commit-v36372
Read this skill before making git commits to ensure consistent, polished messages that conform to the Conventional Commits standard.
Draft a polished conventional commit message for your latest changes.
High-intent search queries and answers about installing and using this skill.
You can automate git commits with conventional messages by enforcing the <type>(<scope>): <subject> format, prompting for a descriptive body, and honoring pre-commit hooks to ensure consistent version control.
The conventional commits format structures git messages as <type>(<scope>): <subject>, followed by a descriptive body explaining what changed and why, ensuring consistent messaging for features, fixes, and refactors.
No, this conventional commits approach avoids automatic pushing. It respects pre-commit hooks and refrains from committing or pushing without a manual review of the generated message and staged changes.
Writing a good conventional commit body for a refactor involves crafting a descriptive explanation detailing what changed in the code and why, guided by prompts that enforce the conventional commits structure.
Yes, you can apply conventional commits across multiple software repositories. This approach enforces consistent commit messaging for features, fixes, and refactors, making it suitable for software projects and teams.
KibertumAnalyze diffs and generate conventional git commit messages with pre-commit checks.
drgaciwGenerate changelogs and release notes from Conventional Commits in CI/CD pipelines.
Kushal9889Sets up Husky git hooks to automate code quality checks and testing before commits.
chuan-khunaAnalyze diffs and generate Conventional Commits messages.
