code-archaeology

# Code Audit Skill **CRITICAL RULE: Never delete data or code files.** Copy to legacy/, never move or delete originals. > Systematically review and understand old code, data, and analysis files. ## Purpose Based on Scott Cunningham's workflow of reviving old projects - understanding what exists, documenting it, and making it safe to work with. **For formal audits with cross-language replication and referee reports, use the Referee 2 agent (`.claude/agents/referee2-reviewer.md`).** This skill is for understanding and documenting existing code, not formal verification. ## When to Use - Returning to an old project after months/years - Taking over code from a coauthor - Before extending existing analysis - R&R requiring you to revisit old work ## When NOT to Use - **Brand new projects** — use project-safety skill instead to set up structure - **Formal code verification** — use the Referee 2 agent for cross-language replication - **Quick code questions** — just ask directly, no need for full audit ## Workflow 1. **Explore the directory**: - What files exist? - What's the structure? - When were things last modified? 2. **Understand the pipeline**: - What are the main scripts? - What order do they run in? - What data do they use? - What outputs do they produce? 3. **Document findings**: - Create/update README.md - Map data flows - Note dependencies 4. **Establish safety**: - Create legacy/ folder - Copy (don't move) originals - Se...