file-edit-safety

name	file-edit-safety
description	Safe file modification procedures following user's strict preferences. Use before ANY file modification - research first, verify changes, never leave things broken.

File Edit Safety Protocol

User's strict rule: Be CAREFUL before modifying any files — research first, verify changes, don't leave things broken.

Mandatory Process

1. BEFORE Editing

• Read current file completely first
• Understand what it does
• Backup/commit current version if possible
• Know what "working" looks like (test/baseline)

2. DURING Editing

• Use patch tool with EXACT unique strings (include surrounding context)
• Make one change at a time
• Verify syntax after each change
• Never batch-edit without understanding each change

3. AFTER Editing

• Syntax check the file
• Verify the change matches intent
• Test if applicable
• If broken - revert immediately

Safe Patterns

Python Files

# After editing, always verify syntax
python3 -m py_compile <file.py>

Config Files (YAML/JSON)

# YAML validation
python3 -c "import yaml; yaml.safe_load(open('file.yaml'))"

# JSON validation
python3 -c "import json; json.load(open('file.json'))"

Shell Scripts

# Syntax check without executing
bash -n <script.sh>

Anti-Patterns to AVOID

• ❌ Writing entire files from scratch (use patch instead)
• ❌ Guessing config keys (check 3-10 sources first)
• ❌ Multiple edits at once (do one, verify, proceed)
• ❌ Assuming file format (read first!)

Quick Recovery

If something breaks:

1. Check git for previous version
2. Restore from backup
3. Tell user what happened and fix it

Decision Framework

Before making a change, ask:

1. Do I understand this file's purpose?
2. Do I know the exact string to replace?
3. Can I verify the change is correct?
4. Can I revert if wrong?

If any answer is NO - research first.