branches

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

Jump to install

Repository: redis/RedisInsight
Last source activity: May 20, 2026 at 07:30
Detected SKILL.md language: English
Stars: 8,736
Forks: 487

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/redis/RedisInsight --skill branches

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

e2e-testing

Playwright end-to-end testing standards for RedisInsight: page object models, test structure, fixtures, navigation patterns, and flaky-test prevention. Use when editing files under tests/e2e-playwright/**, writing Playwright tests, adding page objects, or when the user mentions Playwright, E2E tests, page objects, or end-to-end testing.

2026-08-07

pull-requests

Create and review pull requests following project standards including title format, description template, and review checklist. Use when creating PRs, writing PR descriptions, or reviewing pull requests.

2026-08-03

dead-dependencies

Find and safely remove unused ("dead") npm dependencies in RedisInsight using a grep + leaf-check + build-gate recipe. Use when cleaning up dependencies, investigating whether a package is still used, removing a suspected leftover, or when the user mentions dead deps, unused dependencies, dependency cleanup, leftover packages, or "is this safe to remove". Complements the weekly vulnerability audit (`scripts/dependency-audit-report.mjs`), which only reports vulnerabilities.

2026-07-22

View all from this repository

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

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

branches

Source facts

Install options

Review the source files

More from this repository

Branch Naming Conventions

Branch Types

Issue References

More from this repository

Branch Naming Conventions

Branch Types

Issue References