Rule Prohibiting the Discarding of Changes

Uncommitted changes in the existing working tree or index are valuable user work. Until the task is complete, deleting or discarding these changes is strictly prohibited.

1. List of Prohibited Commands

Running the following commands, including equivalent flags or options, is prohibited.

Discarding changes in the working tree or index
- ```
git reset --hard
```
  /
```
git reset --merge
```
  /
```
git reset --keep
```
  (forcibly resets and erases changes or the index)
- ```
git checkout .
```
  /
```
git checkout -- <file>
```
  (cancels edits in the working tree)
- ```
git checkout -f
```
  /
```
git switch -f
```
  (ignores or overwrites uncommitted changes when switching branches)
- ```
git restore .
```
  /
```
git restore <file>
```
  (discards and restores changes in the working tree or staging area)
- ```
git clean
```
  (physically deletes new untracked files and ignored files)
Deleting files or stashed data (Stash)
- ```
git stash
```
  (risks data loss due to failed stashing or incorrect usage)
- ```
git rm -f
```
  (physically deletes tracked files from the working tree)
- ```
git worktree remove --force
```
  (removes an entire working area that may contain uncommitted changes)
Discarding changes while resolving conflicts
- ```
git checkout --ours
```
  /
```
git checkout --theirs
```
  (completely overwrites and discards one side of the changes during a conflict)
- ```
git merge --abort
```
  /
```
git rebase --abort
```
  (aborts merge or rebase work and discards the changes being resolved)
- ```
git rebase --skip
```
  (skips and discards the changes being applied)
Force-deleting branches or remote history
- ```
git branch -D
```
  (force-deletes an unmerged work-in-progress or stash branch)
- ```
git push --force
```
  /
```
git push -f
```
  (force-overwrites remote history and erases the work log)

2. Detecting and Avoiding Destructive Changes

Before running commands or scripts, check the current state of the working tree.

Status check: Before starting a task, always run
```
git status
```
and verify whether there are any uncommitted changes (Modified / Untracked).
Conflict check: If a file to be changed has already been edited, integrate the new changes without deleting the existing code, or ask the user whether it is acceptable to edit the file.
Handling new files: Even if untracked files (Untracked files) exist, do not delete or clean them up.

3. Safe Alternative Procedures

To proceed safely while preserving changes, choose the appropriate procedure below based on the situation.

If you want to temporarily save changes while working: Create a temporary commit to preserve them.
bash
```
git add .
git commit -m "wip: save uncommitted changes before task"
```
If you want to work on a new branch: Switch to a new branch while preserving the existing changes.
bash
```
git checkout -b feature/your-task-name
```

defensive-git

NPX Install

Tags

SKILL.md Content (Chinese)

Rule Prohibiting the Discarding of Changes

1. List of Prohibited Commands

2. Detecting and Avoiding Destructive Changes

3. Safe Alternative Procedures