Standardize Git commit messages with types, scopes, and subject limits.
npx skills add https://github.com/feraudet/ssii --skill commit-conventions-feraudet
Please help me install this Agent Skill. Skill: commit-conventions Source: https://github.com/feraudet/ssii/tree/main/.claude/skills/commit-conventions Command: npx skills add https://github.com/feraudet/ssii --skill commit-conventions-feraudet
## What problem does it solve? Standardizes Git commit messages to improve project traceability and code review.
## Core Features & Use Cases
### Quick Start Follow the commit-conventions guide to structure your commits as <type>(<scope>): <subject> with optional body and footer when needed.
High-intent search queries and answers about installing and using this skill.
Conventional Git commit messages standardize commit types, scopes, and subject lengths to improve project traceability and streamline code review. They enforce consistent histories across backend, frontend, API, and documentation workflows, making automation and changelog generation easier.
Structure Git commit messages as <type>(<scope>): <subject> with an optional body and footer. Use types like feat, fix, or refactor, and scopes like backend, frontend, api, db, or ui to categorize changes across your development lifecycle.
The maximum character length for a Git commit subject line is 72 characters. Subjects must use the imperative mood to maintain concise, readable histories that streamline review and facilitate DRY practices in release notes generation.
Commit-conventions supports workflows across the entire development lifecycle, including feature work, bug fixes, refactors, and documentation. It applies to backend, frontend, API, and database workflows to ensure consistent project traceability.
The best way to automate changelog generation is by enforcing conventional commit types and scopes within your Git history. Standardized commit messaging facilitates DRY practices, allowing automated tools to parse features, fixes, and refactors directly from the commit log.
Use commit types like feat for new features, fix for bug patches, and refactor for code restructuring without behavior changes. Additional types include style, docs, test, chore, and perf, ensuring clear categorization for project traceability and code review.
ivyStage intended files and write conventional, why-focused commit messages.
plurigridGenerate user-facing changelogs from git commit history.
RyoMurakami1983Automates GitLab project and repository setup for streamlined onboarding and management.
borkwebGenerate conventional git commit messages from staged diffs and repository history.
