audit-replication

name	audit-replication
description	Validate replication package by dispatching the replication-verifier agent in submission mode (checks 1-10). Runs master script, cross-references tables and figures against paper, verifies README completeness for AEA Data Editor compliance. Use before data deposit or journal submission.
disable-model-invocation	true
argument-hint	[replication package directory OR 'here' for current project]
allowed-tools	["Read","Grep","Glob","Write","Bash","Task"]

Audit Replication Package

Run end-to-end validation by dispatching the replication-verifier agent in submission mode (all 10 checks).

Input: $ARGUMENTS — directory containing the replication package. Use here or no argument for the current project.

---

Workflow

Step 1: Locate Package

• If $ARGUMENTS is a directory path: use it
• If $ARGUMENTS is here or empty: use Replication/ if it exists, otherwise project root
• Verify the directory exists and contains scripts

Step 2: Launch replication-verifier Agent (Submission Mode)

Delegate to the replication-verifier agent via Task tool:

Prompt: Audit the replication package at [directory].
Mode: Submission (all 10 checks).
Paper location: paper/main.tex (if exists).

Standard Checks (1-4):
  1. LaTeX compilation
  2. Script execution
  3. File integrity
  4. Output freshness

Submission Checks (5-10):
  5. Package inventory (scripts numbered, master script exists)
  6. Dependency verification (renv.lock, sessionInfo, package versions)
  7. Data provenance (sources documented, no hardcoded paths)
  8. Execution verification (run master script end-to-end)
  9. Output cross-reference (every table/figure traced to script)
  10. README completeness (AEA format)

Save report to quality_reports/replication_audit_[date].md

Step 3: Handle Failures

If execution errors are found (Check 8):

1. Display specific error with file and line number
2. Suggest concrete fix
3. Ask user if they want to fix and re-audit (max 3 iterations)

Step 4: Present Results

# Replication Audit Report
**Date:** [YYYY-MM-DD]
**Mode:** Submission

## Check Results
| # | Check | Status | Details |
|---|-------|--------|---------|
| 1 | LaTeX compilation | PASS/FAIL | |
| 2 | Script execution | PASS/FAIL | |
| 3 | File integrity | PASS/FAIL | |
| 4 | Output freshness | PASS/FAIL | |
| 5 | Package inventory | PASS/FAIL | |
| 6 | Dependencies | PASS/FAIL | |
| 7 | Data provenance | PASS/FAIL | |
| 8 | End-to-end execution | PASS/FAIL | |
| 9 | Output cross-reference | PASS/FAIL | |
| 10 | README completeness | PASS/FAIL | |

## Summary
- Checks passed: N / 10
- **Overall: PASS / FAIL**
- Blocking issues: [list]
- Positive findings: [list]

---

Principles

• This skill runs code. It needs Bash access to execute scripts for Check 8.
• Be patient with runtime. Set appropriate timeouts for long-running packages.
• Don't modify the package during audit. Read and run only.
• Specific errors. "Script 03_robustness.R fails at line 47: object 'treatment_var' not found" beats "execution failed."
• AEA Data Editor standards. The target is full compliance — README format, documented versions, data provenance.