git-safety

Original：🇨🇳 Chinese

Translated

Git Operation Safety and Standards. Mandatory use of native Git commands to handle tracked files, preventing index loss or redundant changes. Triggered when an Agent attempts to move, rename, or delete files.

1installs

Sourceab300819/skills

Added on2026-02-17

NPX Install

npx skill4agent add ab300819/skills git-safety

SKILL.md Content (Chinese)

View Translation Comparison →

Git Safety & Standards

This Skill is designed to ensure security and historical integrity when performing file operations in a Git repository.

Core Guidelines

1. Move & Rename

Prohibited: Direct use of the
```
mv
```
command to manipulate Git-tracked files.
Mandatory: Use
```
git mv <old_path> <new_path>
```
.
Rationale: Ensures Git automatically tracks file restructuring, preserves Git History, and avoids being identified as "delete + add".

2. Delete

Prohibited: Direct use of
```
rm
```
or
```
rm -rf
```
to manipulate Git-tracked files.
Mandatory: Use
```
git rm <path>
```
or
```
git rm -r <path>
```
.
Rationale: Synchronously removes files from both the working directory and index, avoiding residual untracked deletion changes.

3. Pre-Operation Self-Check Process

When an Agent is preparing to operate on files, it should follow this logic:

Check Status: Execute
```
git ls-files <path>
```
.
Judgment:
- If there is output (indicating the file is tracked) → Use
```
git mv
```
  /
```
git rm
```
  .
- If there is no output (indicating the file is untracked) → Use regular
```
mv
```
  /
```
rm
```
  .

Applicable Scenarios

Adjustments to file directory structure due to code refactoring.
Deleting outdated documentation or code files.
Project cleanup.

Constraints

It is strictly forbidden to blindly use regular file management commands without confirming the file status.
Before performing large-scale move operations, it is recommended to execute
```
git status
```
first to ensure the working directory is clean.