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
More from flonat/claude-research
update-focus
Use when you need to update current-focus.md with a structured session summary.
11project-safety
Use when you need to set up safety rules and folder structures for a research project.
11latex-autofix
Use when you need to compile LaTeX with autonomous error resolution and citation audit.
8literature
Use when you need academic literature discovery, synthesis, or bibliography management. Supports standalone searches and end-to-end project pipelines with vault sync and auto-commit.
8pre-submission-report
Use when you need all quality checks run before submission, producing a single dated report.
7process-reviews
Use when you need to process referee comments from a reviews PDF into tracking files.
7