Git Safety Agent Skill
>- 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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/redis/RedisInsight --skill git-safetyThe instruction itself
8 sections, as written by the authorGit Safety Rules for AI Agents
🚫 CRITICAL: Protected Branch Rules
AI agents must NEVER commit to or push to protected branches under any circumstances.
Protected Branches
main- Primary production branchlatest- Latest stable releaserelease/*- Release branches (e.g.,release/v2.0.0)
This is a non-negotiable rule that applies to all scenarios:
Prohibited Actions
- ❌ Direct commits - Never run
git commitwhile on a protected branch - ❌ Direct pushes - Never run
git push origin <protected-branch>orgit pushwhile on a protected branch - ❌ Force pushes - Never run
git push --forceorgit push -ftargeting protected branches - ❌ Merging into protected branches locally - Never run
git merge <branch>while on a protected branch - ❌ Rebasing protected branches - Never run
git rebasewhile on a protected branch - ❌ Resetting protected branches - Never run
git resetwhile on a protected branch
Required Workflow
- Always create a feature branch before making any changes
- Verify current branch before any git operation using
git branch --show-current - Create Pull Requests for all changes - let the review process handle merging
Pre-Push Checklist
Before executing any push command, AI agents must:
- ✅ Confirm current branch is NOT a protected branch (
main,latest,release/*) - ✅ Verify the remote and branch target
Error Recovery
If accidentally on a protected branch with uncommitted changes:
- Stash changes:
git stash - Create new branch:
git checkout -b <appropriate-branch-name> - Apply changes:
git stash pop - Continue work on the new branch
Rationale
- Protected branches represent production-ready or release code
- All changes must go through code review via Pull Requests
- Direct pushes bypass CI/CD checks and team review
- Mistakes on protected branches can affect the entire team and deployment pipeline
Other skills for the same job
different authors, same section of the catalogue
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
How to use it
Take redis/git-safety from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.