Agent skill
safe-file-operations
Guidelines for safely executing destructive file operations (mv, rm, cp). Use when performing file moves, deletions, or overwrites to prevent accidental data loss. Provides verification steps and best practices for batch operations.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/safe-file-operations
SKILL.md
Safe File Operations
CRITICAL: Before running any potentially destructive commands (mv, rm, cp with overwrite, etc.), ALWAYS verify the environment first:
- Check working directory: Run
pwdto confirm you're in the expected location - Verify file existence: Use
ls -la <file>to check files exist and are what you expect - Check file types: Verify if files are regular files or symlinks before operations
- Test on one file first: For batch operations, test the command on a single file before looping
- Verify after operations: Check the result with
ls -lato confirm success
Example safe workflow:
# DON'T DO THIS:
mv CLAUDE.md AGENTS.md # Blind execution
# DO THIS INSTEAD:
pwd # Verify location
ls -la CLAUDE.md # Confirm file exists
mv CLAUDE.md AGENTS.md # Execute
ls -la AGENTS.md # Verify success
For batch operations:
# Test on ONE file first
cd /path/to/first/dir && pwd && ls -la CLAUDE.md && mv CLAUDE.md AGENTS.md && ls -la AGENTS.md
# Only after confirming success, proceed with batch
for dir in ...; do ...; done
The user is trusting you with their files. Be careful!
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?