Create git commit messages with conventional type prefixes and structured bodies.
npx skills add https://github.com/nikuscs/olx-tracker --skill commit-nikuscs
Please help me install this Agent Skill. Skill: commit Source: https://github.com/nikuscs/olx-tracker/tree/main/.claude/skills/commit Command: npx skills add https://github.com/nikuscs/olx-tracker --skill commit-nikuscs
Create a git commit message that follows project conventions to ensure consistency and clarity in version history.
Draft a conventional commit message that uses an appropriate type prefix and a concise subject.
High-intent search queries and answers about installing and using this skill.
To write a conventional commit message, use an appropriate type prefix like feat, fix, docs, refactor, or chore, followed by a concise subject line and a structured body. This ensures version history consistency and clarity for code reviews.
The correct git commit subject line is concise and directly follows the change-type prefix. Using a structured subject line improves reviewability and ensures the commit message adheres to project conventions for automation-friendly formatting.
You create changelog-compatible git commit messages by enforcing conventional change-type prefixes and structured body text. This automation-friendly formatting supports changelog generation and maintains clarity across collaborative repositories.
Yes, conventional commits work in CI workflows by enforcing change-type prefixes and structured bodies that support automation-friendly formatting. This ensures consistent version history and changelog compatibility across collaborative repositories.
The standard conventional commit type prefixes include feat, fix, docs, refactor, and chore. Using these prefixes enforces change-type classification and ensures your git commit messages follow project conventions for better reviewability.
accolverAnalyze staged git diffs to generate conventional commit messages with monorepo scopes.
FaysilAlshareefGenerate changelogs from git commits using Conventional Commits and Keep a Changelog formats.
sunLeeeValidate Git commit messages against Conventional Commits rules.
plurigridGenerate user-facing changelogs from git commit history.
