Generate commit messages following the Conventional Commits specification.
npx skills add https://github.com/redis/RedisInsight --skill commits-redis
Please help me install this Agent Skill. Skill: commits Source: https://github.com/redis/RedisInsight/tree/main/.ai/skills/commits Command: npx skills add https://github.com/redis/RedisInsight --skill commits-redis
It helps you produce consistent, readable commit messages that make project history easier to understand and automate release tooling.
<type>(<scope>): <subject> plus optional body and footer for issue references.Use case example: You implement a new UI search feature and want your history to clearly reflect what changed and link it to a ticket for review and changelog generation.
Use the commits skill when drafting a commit message for your latest change and ask it to format it in Conventional Commits style.
High-intent search queries and answers about installing and using this skill.
To write a conventional commit message, you structure it as <type>(<scope>): <subject>, optionally adding a body and footer. This format applies to feature development, bug fixes, refactoring, tests, and maintenance work.
The conventional commits format uses a structured pattern with an optional footer for issue references. This links your git changes to tickets, making project history easier to understand and automating release notes generation.
Choosing the right commit type involves matching your work to categories like feat for features, fix for bug fixes, and refactor for refactoring. The skill provides type guidance and examples to help you select the appropriate one.
Yes, conventional commits enable reliable tooling for your project history. By enforcing a structured pattern of type, scope, and subject, the format makes project history easier to understand and automate release notes generation.
A conventional commit body should provide meaningful "why" context for your change. Best-practice guardrails encourage adding this explanation while keeping commits atomic and discouraging vague or overly broad messages.
Yes, the conventional commits skill applies to creating commit messages during documentation updates, tests, and maintenance work. It helps you choose an appropriate type and write a concise subject following the formatting rules.
tomlupoGenerate structured Git commit messages from staged changes.
FaysilAlshareefGenerate changelogs from git commits using Conventional Commits and Keep a Changelog formats.
vulikjulikGenerate conventional commit messages from staged git changes.
0xharryriddleDrafts precise Conventional Commit messages for staged diffs with configurable formatting rules.