branches

by redis

Create and name git branches following project conventions. Use when creating branches, checking out new branches, or the user mentions branch naming.

npx skills add https://github.com/redis/redisinsight --skill branches
Download ZIPGitHub
8.7k

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-prefix

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 skills from redis

docs-sync
redis
Analyze master branch implementation and configuration to find missing, incorrect, or outdated documentation in docs/, README.md, and per-package READMEs. Use…
official
implement-command
redis
Add a new Redis command (or command variant) to node-redis end-to-end — the `<NAME>.ts` Command file, its registration with JSDoc in the package…
official
maintainer-review
redis
Review a GitHub issue or pull request URL as a node-redis maintainer, with a staged assessment of whether the claim is real, practically important, already…
official
pr-draft-summary
redis
Create the required PR-ready summary block, branch suggestion, title, and draft description for node-redis. Must be used before the final response whenever the…
official
runtime-behavior-probe
redis
Plan and execute runtime-behavior investigations with temporary TypeScript probe scripts, validation matrices, state controls, and findings-first reports. Use…
official
backend
redis
NestJS backend development patterns for the RedisInsight API: module structure, services, controllers, DTOs, dependency injection, and error handling. Use when…
official
branches
redis
Use lowercase kebab-case with type prefix and issue/ticket identifier. Branch names must match GitHub Actions workflow rules (see .github/workflows/enforce-branch-name-rules.yml ).
official
code-quality
redis
Code-quality standards for RedisInsight: TypeScript strictness, naming conventions (camelCase, PascalCase, UPPER_SNAKE_CASE), linting rules, no `any` without…
official