Create git commits with conventional type prefixes and lowercase subjects.
npx skills add https://github.com/SeloraHomes/ha-selora-ai --skill commit-selorahomes
Please help me install this Agent Skill. Skill: commit Source: https://github.com/SeloraHomes/ha-selora-ai/tree/main/.claude/skills/commit Command: npx skills add https://github.com/SeloraHomes/ha-selora-ai --skill commit-selorahomes
Create git commits that strictly follow conventional commit rules to improve changelogs and release automation.
Write a single-line commit message that starts with a type prefix and a lowercase subject.
High-intent search queries and answers about installing and using this skill.
To write conventional commit messages for automated release pipelines, start your single-line message with a type prefix like feat or fix, followed by a concise lowercase subject to ensure release-friendly changelog generation.
The maximum subject length for conventional commits is 50 characters, including the type prefix. Enforcing this limit maintains readability and compatibility with semantic-release tooling.
To format the body text of a git commit, follow body wrapping guidelines to structure detailed explanations, separating it from the subject to align with conventional commit rules and release automation.
Yes, this commit workflow supports typical chore and fix prefixes alongside feature types, enforcing lowercase formatting and subject length limits across various staged development scenarios.
Your commit fails lint checks before a release because it lacks a conventional type prefix, exceeds the 50-character subject limit, or uses uppercase formatting, disrupting automated release tooling.
RoxabiConfigure commit standards and release automation tools for Node, Bun, Deno, or Python projects.
dhruvinrsoniParse git history to generate changelogs and release notes.
safzanpiraniAutomate Husky pre-commit hook setup with lint-staged for formatting and linting.
TobiasGoetzGenerate conventional commit messages and PR titles for Release Please.
