SkillsAdd

svenja-dev/claude-code-skills

safe-git-guard

Prevents destructive Git operations by requiring backup and confirmation. Blocks git reset --hard, git push --force on main, git clean -fd. Requires backup before git checkout, git reset, git rebase. Activate on any destructive git command.

First seen Jan 24, 2026

Installation

$ npx skills add svenja-dev/claude-code-skills --skill safe-git-guard
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

frontend-design Same topic
anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…

866.4K installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-diagnostics Same topic
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs

Also in this package

Other skills from svenja-dev/claude-code-skills · top by installs.

npx skills add svenja-dev/claude-code-skills
social-media-content 340 project-development 229 reddit-research 102 tdd-strict 67 linkedin-engagement 60 qa-checklist 35 prompt-architect 31 strict-typescript-mode 30 preview-testing 30 code-quality-gate 29

Browse all from svenja-dev/claude-code-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 38
License LICENSE
Default branch main
Open issues 1
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,733 B
  • docs SUMMARY.md 262 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 27 installs

SKILL.md

Safe Git Guard

Skill to prevent destructive Git operations

Trigger

This skill activates automatically on these commands:

  • git reset --hard
  • git checkout -- <file>
  • git clean -fd
  • git rebase (without explicit confirmation)
  • git push --force

Rules

FORBIDDEN (never execute):

  1. git reset --hard - Deletes uncommitted changes irreversibly
  2. git push --force on main/master - Can destroy remote history
  3. git clean -fd - Deletes untracked files irreversibly

WARNING + BACKUP required:

  1. git checkout -- <file> - Overwrites local changes

- BEFORE execution: Create backup - git stash push -m "backup-before-checkout-$(date +%s)"

  1. git reset HEAD~n - Resets commits

- BEFORE execution: Create tag - git tag backup-before-reset-$(date +%s)

  1. git rebase - Modifies history

- BEFORE execution: Create backup branch - git branch backup-before-rebase-$(date +%s)

Workflow for Destructive Operations

1. STOP - Don't execute immediately
2. BACKUP - Save current state (tag/branch/stash)
3. ASK - "Are you sure? What will be lost?"
4. CONFIRM - Explicit "Yes, I understand the risk"
5. EXECUTE - Only then run the command

Example Dialog

User: "Undo the last 3 commits"

Claude (with this skill):

WARNING: DESTRUCTIVE OPERATION DETECTED

You want to run `git reset HEAD~3`. This would:
- Remove 3 commits from history
- Changes become "unstaged" (--soft) or deleted (--hard)

Creating backup:
> git tag backup-YYYYMMDD-pre-reset

Should I proceed? (Answer with "Yes, proceed with reset")

Protected Branches

Configure in your project's CLAUDE.md:

protected_branches:
  - main      # Production branch, never force-push
  - master    # Legacy production branch
  - develop   # Development branch, PR only
  - release/* # Release branches, approval only

Integration with No-Touch Zones

This skill respects No-Touch Zones defined in CLAUDE.md. When changes affect protected files: Additional warning + Impact Analysis.

Configuration

Add to your CLAUDE.md:

### Git Safety Rules

Protected Branches:
- main, develop, release/*

No-Touch Zones (require explicit approval):
- src/auth/**
- src/core/**
- config/production.*

Origin

Originally developed for fabrikIQ - AI-powered manufacturing data analysis.

License

MIT - Free to use and modify