Branches
- 12 installs
- 8.7k repo stars
- Updated August 4, 2026
- redis/redisinsight
branches applies RedisInsight git branch naming conventions.
About
The branches skill defines RedisInsight branch naming as lowercase kebab-case with type prefix and issue reference pattern type/issue-ref/short-title. Internal JIRA uses RI-XXX in paths like feature/RI-123/add-user-profile while open source GitHub issues use numeric refs like feature/123/add-export-feature. Types include feature, bugfix, fe/feature, fe/bugfix for redisinsight/ui only, be/feature, be/bugfix for api only, docs, test, e2e, release/v2.0.0, and ric/ custom prefix. Notes specify bugfix in ui folder should use fe/bugfix instead of bugfix and hash symbols belong in commit messages not branch names.
- Uses type/issue-ref/short-title kebab-case pattern.
- Separates JIRA RI-XXX from GitHub numeric refs.
- Provides fe/ and be/ prefixes for UI or API only changes.
- Documents release and ric special branch prefixes.
- Directs ui-only bugfixes to fe/bugfix prefix.
Branches 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)
branches capabilities & compatibility
- Capabilities
- branch types list · issue references jira vs github · pattern examples block
- Works with
- github · jira
- Use cases
- code review
What branches says it does
Use lowercase kebab-case with type prefix and issue/ticket identifier
npx skills add https://github.com/redis/redisinsight --skill branchesAdd 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 ↗ |
What branch name should I use for RI-123 feature work?
Name git branches using RedisInsight kebab-case type and issue conventions.
Who is it for?
RedisInsight contributors creating feature or fix branches.
Skip if: Skip outside RedisInsight repository conventions.
When should I use this skill?
User creates branches or asks branch naming for RedisInsight.
What you get
Valid branch name matching RedisInsight type and ticket pattern.
Files
Branch 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-prefixBranch 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
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 branches do?
branches applies RedisInsight git branch naming conventions.
When should I use branches?
User creates branches or asks branch naming for RedisInsight.
Is this skill safe to install?
Review the Security Audits panel on this page before installing in production.