agentskills.codes
GI

git-safety

by tamaguiCodingSource

Safety rules and protocols for handling Git operations to prevent data loss.

Git

Install

mkdir -p .claude/skills/git-safety && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/915" && unzip -o skill.zip -d .claude/skills/git-safety && rm skill.zip

Installs to .claude/skills/git-safety

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Git safety rules. INVOKE WHEN: git push, force push, git reset, git clean, destructive git, push force, reset hard. NEVER force push or do destructive git operations.
166 chars✓ has a “when” trigger
Beginner

Key capabilities

  • →Enforce safe Git push workflows
  • →Prevent destructive history changes
  • →Provide safe alternatives to resets
  • →Manage merge conflicts safely

How it works

The skill mandates a strict workflow that prioritizes pulling before pushing and using stashing instead of hard resets to maintain repository history integrity.

Inputs & outputs

You give it
Git command request
You get back
Safe Git command sequence

When to use git-safety

  • →Safely recover from merge conflicts
  • →Sync local branch with remote repository
  • →Stash work instead of resetting
  • →Follow safe push-pull workflow

About this skill

git safety

rules for git operations in this repo.

rules

  • NEVER force push (git push --force or git push -f)
  • NEVER git reset --hard without explicit permission
  • NEVER git clean -fd without explicit permission
  • prefer git stash over git reset
  • always git pull before git push

forbidden commands

these require EXPLICIT user permission:

  • git push --force
  • git push -f
  • git push --force-with-lease
  • git reset --hard
  • git clean -fd
  • git checkout -- . (discards all changes)

safe alternatives

instead of git reset --hard:

  • git stash to save changes
  • git stash pop to restore

instead of force push:

  • git pull --rebase then normal push
  • ask user how to resolve conflicts

workflow

  1. git pull before making changes
  2. make changes
  3. git add relevant files
  4. git commit
  5. git pull again before push
  6. git push (no force flags)

When not to use it

  • →Performing force pushes without explicit permission
  • →Executing destructive commands on shared branches

Limitations

  • →Requires explicit permission for forbidden commands
  • →Strict adherence to workflow rules

How it compares

It explicitly forbids destructive commands and provides safer alternatives to prevent accidental data loss or history corruption.

Compared to similar skills

git-safety side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
git-safety (this skill)36moNo flagsBeginner
resolve-conflicts818moReviewIntermediate
dependency-upgrade265moReviewIntermediate
openspec-onboard106moReviewBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

More by tamagui

View all by tamagui →

tamagui

tamagui

Universal React UI framework for web and native. Use when building cross-platform apps with Tamagui, creating styled components with `styled()`, configuring design tokens/themes, using Tamagui UI components, or working with animations. Triggers: "tamagui", "styled()", "$token", "XStack/YStack", "useTheme", "@tamagui/*" imports, "createStyledContext", "variants".

2478

release-safety

tamagui

Release safety rules. INVOKE WHEN: yarn release, npm publish, release canary, release packages, publishing, skip checks, skip tests. NEVER skip checks or tests without explicit permission.

13

You might also like

resolve-conflicts

antinomyhq

Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.

81334

dependency-upgrade

wshobson

Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.

26240

openspec-onboard

studyzy

Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.

10207

codex-cli-bridge

alirezarezvani

Bridge between Claude Code and OpenAI Codex CLI - generates AGENTS.md from CLAUDE.md, provides Codex CLI execution helpers, and enables seamless interoperability between both tools

9180

skill-sync

KyleKing

Syncs Claude Skills with other AI coding tools like Cursor, Copilot, and Codeium by creating cross-references and shared knowledge bases. Invoke when user wants to leverage skills across multiple tools or create unified AI context.

12130

git-commits

bonny

Create well-structured git commits in logical chunks following best practices

21109

Search skills

Search the agent skills registry