Commits
- 12 installs
- 8.7k repo stars
- Updated August 4, 2026
- redis/redisinsight
commits generates Conventional Commits messages for RedisInsight.
About
The commits skill enforces Conventional Commits format type(scope): subject with optional body and footer for RedisInsight. Types include feat, fix, refactor, test, docs, chore, style, perf, and ci with scopes such as ui or api. Good examples show atomic changes, why explanations, and References #RI-123 or Fixes #456 footers for JIRA and GitHub auto-linking. Bad examples warn against vague WIP messages and overly broad multi-topic commits. Best practices demand concise bodies without listing every file change.
- Uses Conventional Commits type scope subject format.
- Links JIRA RI tickets and GitHub issues in footers.
- Encourages atomic single-logical-change commits.
- Explains why in body not just what changed.
- Lists good versus bad commit message examples.
Commits by the numbers
- 12 all-time installs (skills.sh)
- +1 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #415 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
commits capabilities & compatibility
- Capabilities
- commit types list · good and bad commits examples · issue references jira github
- Works with
- github · jira
- Use cases
- code review · documentation
What commits says it does
Atomic changes (one logical change per commit)
npx skills add https://github.com/redis/redisinsight --skill commitsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 12 |
|---|---|
| repo stars | ★ 8.7k |
| Last updated | August 4, 2026 |
| Repository | redis/redisinsight ↗ |
How should I format a RedisInsight commit message?
Write Conventional Commits messages for RedisInsight with issue references.
Who is it for?
RedisInsight contributors writing git commit messages.
Skip if: Skip for repos without Conventional Commits policy.
When should I use this skill?
User creates commits or asks commit message format.
What you get
Conventional commit with scope, body, and issue reference footer.
Files
Commit 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.2Best 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 testsIssue References
- JIRA (internal):
References: #RI-123orFixes #RI-123 - GitHub (open source):
Fixes #456orCloses #456 - Use
#for auto-linking in commit messages
Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148FAQ
What does commits do?
commits generates Conventional Commits messages for RedisInsight.
When should I use commits?
User creates commits or asks commit message format.
Is this skill safe to install?
Review the Security Audits panel on this page before installing in production.