delete-content

# Delete Content Skill

Generic file deletion Skill that checks RULE.md permissions and handles dependencies safely.

## When to use this Skill

- User says "delete", "remove", "trash"
- User requests content deletion
- User wants to clean up old files

## Workflow

### 1. Identify Target File

**If user provides file path**:
- Verify file exists using `ls` or Read
- Confirm file identity

**If user provides topic/title only**:
- Search for file using Grep or Glob
- Pattern: `**/*keyword*.md`
- If multiple matches: present list, ask user to choose
- If no matches: report not found

**Search strategies**:
1. Filename match: `find . -name "*keyword*"`
2. Content match: `grep -r "keyword" .`
3. README.md index: Search README.md files for references

### 2. Read Directory RULE.md

**Locate and read RULE.md**:
1. Check file's directory for RULE.md
2. If not found, check parent directories (inheritance)
3. Parse RULE.md for deletion rules

**Check for**:
- Are deletions allowed? (some directories may be immutable or archive-only)
- Archive-instead rules (move to archive instead of delete)
- Backup requirements (create backup before delete)
- Dependency rules (check cross-references)
- Confirmation requirements

**Example RULE.md deletion rules**:
```markdown
## Deletion Rules
- Deletions allowed with confirmation
- Check for cross-references before deleting
- Move to Archive/ subdirectory instead of permanent deletion
```

### 3. Check Dependencies

**Search for cross-references**:
1. Use Grep to find links to this file: `grep -r "filename" .`
2. Search for references in README.md files
3. Check for reverse links (files this file links to)
4. Identify files that depend on this content

**Categorize dependencies**:
- **Incoming**: Files that link to this file (will break if deleted)
- **Outgoing**: Files this file links to (won't break, but orphans references)
- **Bidirectional**: Cross-referenced files (mutual dependencies)

**Severity assessment**:
- Critical: Many incom