Standardize Git commit messages with conventional format and scope guidance.
npx skills add https://github.com/jasonencode/saas --skill git-commit-jasonencode
Please help me install this Agent Skill. Skill: git-commit Source: https://github.com/jasonencode/saas/tree/main/.trae/skills/git-commit Command: npx skills add https://github.com/jasonencode/saas --skill git-commit-jasonencode
Git commit messages are often inconsistent, making code review and project history hard to follow. This skill standardizes messages to improve readability, traceability, and collaboration.
Start by applying the conventional commit format to your next commit.
High-intent search queries and answers about installing and using this skill.
Conventional commits standardize Git messages by defining a structured format with a type, optional scope, and description. This improves readability, traceability, and collaboration across software development workflows.
To write a Git commit message for a feature, use the conventional format like feat(auth): add login flow. This applies a defined types table and scope guidance to ensure clear project history and easier code review.
Common commit types include fix, docs, and refactor, defined in a types table to guide commits across specific scenarios. Using these types standardizes messages for precise code review and changelog generation.
Yes, this standardizes Git commit messages with pre-commit hook support to enforce formatting rules automatically. It validates the header and optional body or footer before a commit is finalized.
The best way to format Git commit messages for code review is applying a conventional format with a defined types table and scope guidance. This standardizes headers and bodies to boost teamwork and readability.
You include an optional body and footer in a conventional commit to provide additional context beyond the header. This structured formatting rule helps explain the change and generate detailed changelogs.
missdeerCreate local git commits with conventional commit message formatting.
FaysilAlshareefGenerate changelogs from git commits using Conventional Commits and Keep a Changelog formats.
sunLeeeValidate Git commit messages against Conventional Commits rules.
hairihouEnforce Conventional Commits syntax for Git commit messages and branch naming.
