Official agent skill

Git Safety

by redis in redis/RedisInsight

Critical safety guardrails for protected branches: never commit, push, or force-push directly to main, latest, or release branches; no destructive history rewrites without explicit user approval.

OfficialCustom licenceAuto-check passedDevelopment

Install Git Safety

skills CLI
$ npx skills add redis/RedisInsight --skill git-safety -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install redis/RedisInsight git-safety --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/redis/RedisInsight.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.ai/skills/git-safety .claude/skills/git-safety && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
git-safety
GitHub stars
8.9k
Token cost
~607 tokens
SKILL.md length
272 words
Files
1
Skills in repo
15
Repo updated
First seen
Licence
Custom licence

At a glance

Critical safety guardrails for protected branches: never commit, push, or force-push directly to main, latest, or release branches; no destructive history rewrites without explicit user approval.

  • Works in 3 steps: Always create a feature branch before… → Verify current branch before any git… → Create Pull Requests for all changes -…
  • Asks about merging
  • SKILL.md covers 🚫 CRITICAL: Protected Branch… and Rationale
  • Calls git

What it does

Git Safety is an agent skill from redis/RedisInsight, published by the product's own GitHub organization. Critical safety guardrails for protected branches: never commit, push, or force-push directly to main, latest, or release branches; no destructive history rewrites without explicit user approval. Use before any git operation that touches protected branches, before force-push, reset --hard, history rewrite, or branch deletion, or whenever the user asks about merging, pushing, or release branches.

Its SKILL.md is about 610 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Git workflow. It works with Git and Redis.

When your agent uses it

  • Asks about merging
  • Release branches

Example prompts

  • “/git-safety”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Always create a feature branch before making any changes
  2. Verify current branch before any git operation using git branch --show-current
  3. Create Pull Requests for all changes - let the review process handle merging

What it can do on your machine

Read from SKILL.md and the folder at commit 43bd288. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Git Safety loads about 607 tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 272 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~102
When it runs · the whole SKILL.md, loaded when a task matches
~607

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 272 words (~607 tokens).

“AI agents must NEVER commit to or push to protected branches under any circumstances.”

— opening of SKILL.md by redis, Custom licence
name
git-safety

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .ai/skills/git-safety of redis/RedisInsight.

Open the folder on GitHubat commit 43bd288

Compare with similar skills

Git Safety next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Git Safety compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Git Safety this skillredis/RedisInsight8.9k—~607Automated safety check: PassCustom licence
Creating Description For Gh PRredis/jedis12k—~838Automated safety check: PassMIT
Go-Redis Release Preparationredis/go-redis22k—~1.1kAutomated safety check: PassBSD-2-Clause
E2b Sandboxagent-sandbox/agent-sandbox218—~2.6kAutomated safety check: PassApache-2.0
GitHubswarmclawai/swarmclaw687—~820Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT

Similar skills

  • Official

    Generate a clear, concise GitHub PR title and description from the diff between two local git branches, and save it to prDescription.md in the repo root.

    12k GitHub stars~838 tokensUpdated today
    DevelopmentAuto-check passed
  • Official

    Prepares a go-redis release locally: picks the next semver, gathers merged PRs, writes the RELEASE-NOTES entry and bumps versions, without publishing.

    22k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • E2b Sandbox

    agent-sandbox/agent-sandbox

    Create, manage, and use E2B sandboxes — run commands, manage files, use git, persist state, and configure networking.

    218 GitHub stars~2.6k tokensUpdated 17 days ago
    DevelopmentAuto-check passed
  • GitHub

    swarmclawai/swarmclaw

    GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries.

    687 GitHub stars~820 tokensUpdated 3 mo ago
    DevelopmentAuto-check passed
  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed

More from redis/RedisInsight

All 15 skills in this repo
  • Redis Insight Plugin

    redis/RedisInsight

    Official

    A skill your agent uses when creating, modifying, debugging, deploying, or testing Redis Insight Workbench visualization plugins, plugin manifests, package.json visualizations, activationMethod…

    8.9k GitHub stars~3.5k tokensUpdated 3 days ago
    Auto-check passed
  • Backend

    redis/RedisInsight

    Official

    NestJS backend development patterns for the RedisInsight API: module structure, services, controllers, DTOs, dependency injection, and error handling.

    8.9k GitHub stars~1.6k tokensUpdated 3 days ago
    Auto-check passed
  • Code Quality

    redis/RedisInsight

    Official

    Code-quality standards for RedisInsight: TypeScript strictness, naming conventions (camelCase, PascalCase, UPPERSNAKECASE), linting rules, no any without reason, no !important in styles, and…

    8.9k GitHub stars~1.2k tokensUpdated 3 days ago
    Auto-check passed
  • Commits

    redis/RedisInsight

    Official

    Generate commit messages following Conventional Commits format.

    8.9k GitHub stars~451 tokensUpdated 3 days ago
    Auto-check passed
  • Dead Dependencies

    redis/RedisInsight

    Official

    Find and safely remove unused ("dead") npm dependencies in RedisInsight using a grep + leaf-check + build-gate recipe.

    8.9k GitHub stars~1.5k tokensUpdated 3 days ago
    Auto-check passed
  • E2E Testing

    redis/RedisInsight

    Official

    Playwright end-to-end testing standards for RedisInsight: page object models, test structure, fixtures, navigation patterns, and flaky-test prevention.

    8.9k GitHub stars~5.1k tokensUpdated 3 days ago
    Auto-check passed

Works with

Questions about Git Safety

What does Git Safety do?

Critical safety guardrails for protected branches: never commit, push, or force-push directly to main, latest, or release branches; no destructive history rewrites without explicit user approval. Git Safety is an agent skill from redis/RedisInsight, published by the product's own GitHub organization. Critical safety guardrails for protected branches: never commit, push, or force-push directly to main, latest, or release branches; no destructive history rewrites without explicit user approval.

When should I use Git Safety?

Git Safety fits situations like: asks about merging; release branches.

How do I install Git Safety in Claude Code?

Run `npx skills add redis/RedisInsight --skill git-safety -a claude-code`. Or copy the skill folder (.ai/skills/git-safety in redis/RedisInsight) into .claude/skills/git-safety in your project. Claude Code loads it when a task matches its description.

How do I install Git Safety in Codex?

Run `npx skills add redis/RedisInsight --skill git-safety -a codex`. Or copy the skill folder (.ai/skills/git-safety in redis/RedisInsight) into .agents/skills/git-safety in your project. Codex loads it when a task matches its description.

Can I use Git Safety in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add redis/RedisInsight --skill git-safety -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/git-safety, .gemini/skills/git-safety, .github/skills/git-safety and .opencode/skills/git-safety in your project.

What does Git Safety need to run?

Going by SKILL.md and its folder, Git Safety needs the command-line tools its instructions call (git).

Does Git Safety access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Git Safety safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Git Safety use?

Git Safety has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Git Safety use?

About 607 tokens (SKILL.md is roughly 2.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Git Safety?

Skills that share tags, products or a category with Git Safety: Creating Description For Gh PR (redis/jedis, 12k stars), Go-Redis Release Preparation (redis/go-redis, 22k stars), E2b Sandbox (agent-sandbox/agent-sandbox, 218 stars) and GitHub (swarmclawai/swarmclaw, 687 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Git Safety?

redis (a GitHub organization, an official publisher) maintains it in redis/RedisInsight, which has 8,882 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 4, 2026.

Source: redis/RedisInsight on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.