Commits Agent Skill
>- Generate commit messages following Conventional Commits format. Use when creating commits, writing commit messages, or the user asks to commit changes.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/redis/RedisInsight --skill commitsThe instruction itself
7 sections, as written by the authorCommit Message Guidelines
Follow Conventional Commits format:
<type>(<scope>): <subject>
<body>
<footer>
Commit Types
feat- New featurefix- Bug fixrefactor- Code refactoringtest- Adding or updating testsdocs- Documentation changeschore- Maintenance tasksstyle- Code style changes (formatting)perf- Performance improvementsci- CI/CD changes
Examples
feat(ui): add user search functionality
Implements real-time search with debouncing.
References: #RI-123
---
fix(api): resolve memory leak in connection pool
Properly cleanup subscriptions on unmount.
Fixes #456
---
test(ui): add tests for data serialization
refactor(api): extract common validation logic
docs: update API endpoint documentation
chore: upgrade React to version 18.2
Best Practices
✅ Good Commits
- Clear, descriptive subject line
- Atomic changes (one logical change per commit)
- Reference issue/ticket in body
- Explain why, not just what
- Keep it concise - Don't list every file change in the body
feat(ui): add user profile editing
Allows users to update their profile information including
name, email, and avatar. Includes validation and error handling.
References: #RI-123
❌ Bad Commits
# Too vague
fix stuff
WIP
update
# Too broad
add feature, fix bugs, refactor code, update tests
Issue References
- JIRA (internal):
References: #RI-123orFixes #RI-123 - GitHub (open source):
Fixes #456orCloses #456 - Use
#for auto-linking in commit messages
Other skills for the same job
different authors, same section of the catalogue
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.
Master ES6+ features including async/await, destructuring, spread operators, arrow functions, promises, modules, iterators, generators, and functional programming patterns for writing clean, efficient JavaScript code. Use when refactoring legacy code, implementing modern patterns, or optimizing JavaScript applications.
Master ES6+ features including async/await, destructuring, spread operators, arrow functions, promises, modules, iterators, generators, and functional programming patterns for writing clean, efficient JavaScript code. Use when refactoring legacy code, implementing modern patterns, or optimizing JavaScript applications.
Guidelines and format for writing pull request descriptions in this repository. Use this skill whenever the user asks you to draft a pull request description, submit a PR, or update a PR description.
Angular performance optimization and best practices guide. Use when writing, reviewing, or refactoring Angular code for optimal performance, bundle size, and rendering efficiency.
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions. Uses `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treats external providers (for example Buildkite) as out of scope and reports only the details URL. Do NOT use for addressing PR review comments (use gh-address-comments) or general CI outside GitHub Actions.
Angular performance optimization and best practices guide. Use when writing, reviewing, or refactoring Angular code for optimal performance, bundle size, and rendering efficiency.
How to use it
Take redis/commits from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.