skills.rest
redis
redisOFFICIAL
Explore all skills by this author →
WebsiteGitHub

branches

Generate standardized Git branch names with type prefixes and issue references.

8.7k|482|Updated Jul 30, 2021
Search Tags:#git#frontend#conventions#jira#kebab-case#branch naming#release branching
One-click install
npx skills add https://github.com/redis/RedisInsight --skill branches
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: branches
Source: https://github.com/redis/RedisInsight/tree/main/.ai/skills/branches
Command: npx skills add https://github.com/redis/RedisInsight --skill branches

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams avoid inconsistent or invalid Git branch names by enforcing a clear convention that includes branch type, issue reference, and a short, descriptive title.

Core Features & Use Cases

  • Standardized branch naming: Produces branch names in the expected lowercase kebab-case format with required type prefixes and issue/ticket identifiers.
  • Team-aware prefixes: Supports both internal (JIRA-style RI-XXX) and open source (GitHub issue number) branch reference patterns, plus special-case prefixes like release or custom prefixes.
  • Correct category selection: Guides branch type choice (feature, bugfix, fe/, be/, docs, test, e2e, release, ric) based on where the change applies and what work is being done.

Quick Start

Use the skill to generate a branch name for a frontend-only bug fix in redisinsight/ui related to RI-345, titled fix-login-timeout.

Frequently Asked Questions about branches

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a Git branch name with kebab-case and a JIRA ticket reference?▼

To generate a Git branch name with kebab-case and a JIRA reference, provide the branch type, issue identifier, and short title. The tool formats standard prefixes like feature/ or bugfix/ combined with the RI-XXX ticket ID.

What is the standard naming convention for frontend and backend Git branches?▼

The standard naming convention for frontend and backend Git branches uses specific prefixes such as fe/feature/ or be/bugfix/. This separates workstreams while maintaining lowercase kebab-case formatting and required issue references.

How do I create a release branch name following versioning conventions?▼

To create a release branch name following versioning conventions, use the special release/vX.Y.Z pattern. This structure applies a standardized prefix and semantic version tag directly to the branch name.

Can I use GitHub issue numbers instead of internal RI-XXX references in branch names?▼

Yes, you can use GitHub issue numbers instead of internal RI-XXX references. The tool validates and supports both internal JIRA-style identifiers and open source GitHub numeric patterns for branch naming.

How do I add a custom prefix to an internal RI-XXX Git branch?▼

To add a custom prefix to an internal RI-XXX Git branch, use the special ric/RI-XXX/custom-prefix pattern. This applies your custom text while preserving the required internal ticket identifier.

Related Skills

Explore More Software Engineering Skills→
sergicalsergical
1

create-branch

Create Git branches with Sentry naming conventions and kebab-case names.

Community
Intermediate
LarryHsiaoLarryHsiao

branch

Switch Git branches safely by stashing or temporarily committing uncommitted changes.

Community
Intermediate
YoshikemoloYoshikemolo
5

git-jira-integration

Generate Git branch names and validate commit messages against Jira issues.

Community
Intermediate
thimsluggathimslugga

git-branch-practices

Enforce standard git branch naming with type prefixes and lowercase hyphenated descriptions.

Community
Intermediate