Back to Details

git-safety

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Git Safety & Standards

Git Safety & Standards

该 Skill 旨在确保在 Git 仓库中进行文件操作时的安全性和历史完整性。
This Skill is designed to ensure security and historical integrity when performing file operations in a Git repository.

核心准则

Core Guidelines

1. 移动与重命名 (Move & Rename)

1. Move & Rename

  • 禁止直接使用 
    mv
    命令操作受 Git 跟踪的文件。
  • 强制使用 
    git mv <old_path> <new_path>
    。
  • 理由：确保 Git 自动跟踪文件重构，保留文件的 Git History，避免识别为“删除 + 新增”。
  • 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)

2. Delete

  • 禁止直接使用 
    rm
    或 
    rm -rf
    操作受 Git 跟踪的文件。
  • 强制使用 
    git rm <path>
    或 
    git rm -r <path>
    。
  • 理由：直接从工作区和索引中同步移除，避免残留未跟踪的删除变更。
  • 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. 操作前自检流程

3. Pre-Operation Self-Check Process

当 Agent 准备操作文件时，应遵循以下逻辑：
  1. 检查状态：执行 
    git ls-files <path>
    。
  2. 判断：
    • 如果有输出（说明文件受控）→ 使用 
      git mv
      / 
      git rm
      。
    • 如果无输出（说明是未跟踪文件）→ 使用普通 
      mv
      / 
      rm
      。
When an Agent is preparing to operate on files, it should follow this logic:
  1. Check Status: Execute 
    git ls-files <path>
    .
  2. 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

  • 严禁在未确认文件状态的情况下盲目使用普通文件管理命令。
  • 在执行大规模移动操作前，建议先执行 
    git status
    确保工作区是干净的。
  • 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.