commits
Generate commit messages following Conventional Commits format. Use when creating commits, writing commit messages, or the user asks to commit changes.
Install
With your agent
Install OMGSkills skill "redis/redisinsight:commits" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/redis/RedisInsight /tmp/RedisInsight && ln -s /tmp/RedisInsight/.ai/skills/commits ~/.claude/skills/commits
From README
Commit Message Guidelines Follow Conventional Commits format: Commit Types feat - New feature fix - Bug fix refactor - Code refactoring test - Adding or updating tests docs - Documentation changes chore - Maintenance tasks style - Code style changes (formatting) perf - Performance improvements ci - CI/CD changes Examples 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 ❌ Bad Commits Issue References JIRA (internal): References: #RI-123 or Fixes #RI-123 GitHub (open source): Fixes #456 or Closes #456 Use # for auto-linking in commit messages
