privacy-redactlisted

# /privacy-redact Scan and redact private content from a file before publishing it. ## Usage ``` /privacy-redact <file-path> ``` ## What it scans for | Pattern | Action | |---|---| | System usernames (configured per project) | Remove | | Absolute paths (`/home/<user>/`, `/media/<user>/`, `/mnt/<uuid>/`) | Replace with `~` (relative) or `<workspace>/` | | Token-shaped strings (matching `sk-…`, `ghp_…`, `gho_…`, `github_pat_…` patterns) | **STOP and warn the user** — refuse to write the file with secrets present | | Email addresses (`<user>@<domain>`) | Remove or replace with `<redacted-email>` | | Project-specific codenames | Per project's redaction map (defined in `docs/CONTRIBUTING.md` of the project) | ## Steps 1. **Read** the file 2. **Multi-pattern grep** to find matches (adjust `<your-username>` per project): ```bash grep -nE '<your-username>|/home/|/media/|/mnt/|@gmail|@hotmail|sk-[A-Za-z]|ghp_[A-Za-z0-9]|gho_|github_pat_' <file> ``` 3. **Per match**, show the line and proposed replacement 4. **Ask the user to confirm** batch redaction (or per-line if uncertain). Default to ask — privacy-redact is irreversible w.r.t. the original wording. 5. **Apply** via Edit (one Edit per replacement, or replace_all where safe) 6. **Re-scan** to confirm clean 7. **Report** — show what was redacted and what remains as-is ## When to use - Promoting a draft file to a public location (e.g., `DISCOVERY.md` → `recommendations/*.md`) - Before opening a PR with private con