Generate conventional git commit messages from staged changes.
npx skills add https://github.com/PanJason/Awesome_SDE_Skills --skill commit-panjason
Please help me install this Agent Skill. Skill: commit Source: https://github.com/PanJason/Awesome_SDE_Skills/tree/main/Common/git-commit Command: npx skills add https://github.com/PanJason/Awesome_SDE_Skills --skill commit-panjason
Creating consistent, well-formed git commits is time-consuming and error-prone; this skill automates the generation of conventional commits to improve changelogs and reviews.
Stage your changes and run /commit to generate a conventional commit message.
High-intent search queries and answers about installing and using this skill.
You can generate conventional commit messages by staging your git changes and running the automation command. It parses the staged diff to output a standardized <type>(<scope>): <description> format.
To enforce standard git commit formats, integrate this automation into your CI pipelines. It ensures commit history consistency by requiring structured messages with types like feat, fix, docs, and refactor.
The conventional commits format structures messages as <type>(<scope>): <description>, with optional body and footers. Supported types include feat, fix, docs, style, refactor, test, and chore.
Yes, conventional commits support an optional body and footers alongside the required header. The automation generates these elements from your staged changes to provide detailed context.
Using conventional commits creates an easily parsable commit history, which improves changelog generation and code reviews. It standardizes features, fixes, and maintenance tasks across the project.
mgoodman60Generate descriptive Git commit messages from repository changes with conventional formatting.
AstrumonGenerate Keep a Changelog entries from Conventional Commits history.
DrLuggelsGenerate changelogs and release notes from Conventional Commits.
kevinrobaynaGenerate conventional Git commit messages from analyzed code changes.
