AgentSkillsCN

git-safety-guard

为Claude Code安装Git安全防护钩子，防止破坏性的Git和文件系统命令。 阻止诸如‘git checkout --’、‘git reset --hard’、‘git clean -f’、‘git push --force’和‘rm -rf’等命令导致意外的数据丢失。 使用此技能在新仓库或现有仓库中设置安全防护，或为代理全局设置。

SKILL.md
--- frontmatter
name: git-safety-guard
description: |
  Installs a Git safety guard hook for Claude Code to prevent destructive Git and filesystem commands.
  Blocks accidental data loss from commands like 'git checkout --', 'git reset --hard', 'git clean -f', 'git push --force', and 'rm -rf'.
  Use this skill to set up safety rails in a new or existing repository, or globally for the agent.
tags: [git, safety, setup, hooks, protection]
allowed-tools:
  - Bash(git-safety-guard/install.sh:*)

Git Safety Guard

Installs a PreToolUse hook that intercepts and blocks destructive Bash commands.

Usage

1. Install Globally (Recommended)

Protects the agent across all projects.

bash
git-safety-guard/install.sh --global

2. Install Per-Project

Protects only the current project.

bash
git-safety-guard/install.sh

What It Blocks

Command PatternWhy It's Dangerous
git checkout -- <files>Discards uncommitted changes permanently
git restore <files>Same as checkout -- (newer syntax)
git reset --hardDestroys all uncommitted changes
git reset --mergeCan lose uncommitted changes
git clean -fRemoves untracked files permanently
git push --forceDestroys remote history
git push -fSame as --force
git branch -DForce-deletes branch without merge check
rm -rf (non-temp paths)Recursive file deletion (except /tmp, /var/tmp, $TMPDIR)
git stash dropPermanently deletes stashed changes
git stash clearDeletes ALL stashed changes

Safety Mechanism

The hook is a Python script (git_safety_guard.py) registered in .claude/settings.json (or ~/.claude/settings.json). It runs before every Bash command execution. If a command matches a destructive pattern:

  1. •The command is BLOCKED (never runs).
  2. •The agent receives a "permissionDecision: deny" response with an explanation.

Important Notes

  • •Restart Required: You must restart the agent/session for the hook to take effect after installation.
  • •Overrides: If a destructive command is truly needed, the user must run it manually or the agent must ask for explicit permission (though the hook will still block it if the agent tries to run it directly; the agent must guide the user to run it).