Branches Agent Skill
>- Create and name git branches following project conventions. Use when creating branches, checking out new branches, or the user mentions branch naming.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/redis/RedisInsight --skill branchesThe instruction itself
3 sections, as written by the authorBranch Naming Conventions
Use lowercase kebab-case with type prefix and issue/ticket identifier.
# Pattern: <type>/<issue-ref>/<short-title>
# INTERNAL (JIRA - RI-XXX)
feature/RI-123/add-user-profile
bugfix/RI-789/memory-leak
fe/feature/RI-567/add-dark-mode
be/bugfix/RI-345/fix-redis-connection
docs/RI-333/update-docs
test/RI-444/add-unit-tests
e2e/RI-555/add-integration-tests
# OPEN SOURCE (GitHub - XXX)
feature/123/add-export-feature
bugfix/789/fix-connection-timeout
# Special branches
release/v2.0.0
ric/RI-666/custom-prefix
Branch Types
feature/- New features and refactoring (affects multiple areas)bugfix/- Bug fixes (affects multiple areas)fe/feature/- Frontend-only features (onlyredisinsight/ui/folder)fe/bugfix/- Frontend-only bug fixes (onlyredisinsight/ui/folder)be/feature/- Backend-only features (onlyredisinsight/api/folder)be/bugfix/- Backend-only bug fixes (onlyredisinsight/api/folder)docs/- Documentation changestest/- Test-related changese2e/- End-to-end test changesrelease/- Release branchesric/- 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
Other skills for the same job
different authors, same section of the catalogue
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
How to use it
Take redis/branches 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.