Draft structured commit messages with type, subject, body, and footer.
npx skills add https://github.com/LaHienitaUpegui/Portfolio --skill good-commits
Please help me install this Agent Skill. Skill: good-commits Source: https://github.com/LaHienitaUpegui/Portfolio/tree/main/.agents/skills/good-commits Command: npx skills add https://github.com/LaHienitaUpegui/Portfolio --skill good-commits
Generates well-structured, meaningful commit messages that follow industry best practices.
Draft a concise, conventional commit message for your latest change.
High-intent search queries and answers about installing and using this skill.
To write conventional commit messages for git, draft concise entries using a structured format with type, subject, body, and optional footer, ensuring the subject stays under 50 characters in imperative mood.
The best way to format atomic commits for code refactoring is to generate a structured message per file change, applying type, subject, and body fields to isolate logical modifications for easier review workflows.
A 50-character subject limit improves code quality by forcing concise summaries of code changes, making version control history easier to scan and maintaining an imperative mood for clear commit documentation.
Yes, you can use structured commit messages for software projects of any size, applying conventional commit-like formats across features, fixes, docs, and refactors to maintain consistent version control documentation.
Your git workflow needs atomic commits per file to isolate distinct logical changes, preventing mixed feature and fix documentation in a single commit and streamlining the code review process.
mgoodman60Generate descriptive Git commit messages from repository changes with conventional formatting.
dus2183-commitsGenerate Keep a Changelog formatted CHANGELOG.md from git history and conventional commits.
aaddrickLint shell scripts with shellcheck and GitHub Actions workflows with actionlint.
borkwebGenerate conventional git commit messages from staged diffs and repository history.
