branches
Create and name git branches following project conventions. Use when creating branches, checking out new branches, or the user mentions branch naming.
Install
With your agent
Install OMGSkills skill "redis/redisinsight:branches" into this agent's normal skills directory: use the OMGSkills MCP get_skill tool, install only the pinned_install commit and path, verify SKILL.md against pinned_install.skill_md_sha, 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/branches ~/.claude/skills/branchesFrom README
Branch Naming Conventions Use lowercase kebab-case with type prefix and issue/ticket identifier. Branch Types feature/ - New features and refactoring (affects multiple areas) bugfix/ - Bug fixes (affects multiple areas) fe/feature/ - Frontend-only features (only redisinsight/ui/ folder) fe/bugfix/ - Frontend-only bug fixes (only redisinsight/ui/ folder) be/feature/ - Backend-only features (only redisinsight/api/ folder) be/bugfix/ - Backend-only bug fixes (only redisinsight/api/ folder) docs/ - Documentation changes test/ - Test-related changes e2e/ - End-to-end test changes release/ - Release branches ric/ - Custom prefix for special cases Note: When a bug fix affects only the redisinsight/ui/ folder, use fe/bugfix/ prefix instead of bugfix/. Issue References Internal: RI-XXX (JIRA ticket) Open Source: XXX (GitHub issue number) Use # only in commit messages, not branch names
More from this repo
commits
Used to generate commit messages following Conventional Commits format.
feature-flags
Create, modify, and remove feature flags in RedisInsight.
pull-requests
Used to create and review pull requests following project standards including title format, description template, and...