research-repo-reproduction

Original：🇺🇸 English

Translated

Use when inspecting, cleaning, understanding, reproducing, or auditing academic research code repositories, especially when README commands, datasets, checkpoints, experiments, or paper claims need verification.

3installs

Sourcevincenzoimp/academic-research-skills

Added on2026-05-20

NPX Install

npx skill4agent add vincenzoimp/academic-research-skills research-repo-reproduction

SKILL.md Content

View Translation Comparison →

Research Repo Reproduction

Reproduction means a faithful, documented attempt to run or inspect the research artifact. It does not mean changing anything until the result looks good.

Read First

```
references/repository-contract.md
```
```
references/output-contracts.md
```

Trusted Reproduction Flow

Read README, configs, environment files, scripts, and docs.
Inventory documented commands.
Identify the smallest trustworthy target: smoke test, inference, evaluation, or training startup.
Record assumptions about data, weights, environment, and hardware.
Run only documented or clearly justified commands.
If patching is required, isolate patch notes from scientific contribution claims.
Write standardized evidence under
```
repro_outputs/
```
.

Output Files

```
repro_outputs/SUMMARY.md
```
```
repro_outputs/COMMANDS.md
```
```
repro_outputs/LOG.md
```
```
repro_outputs/PATCHES.md
```
```
repro_outputs/status.json
```

Boundaries

Do not silently change datasets, splits, metrics, checkpoints, or evaluation code.
Do not convert a failed reproduction into an exploratory refactor without naming the transition.
Do not claim SOTA or correctness from a smoke test.
Keep trusted reproduction separate from
```
explore_outputs/
```
.

Repository Cleanup

For bad academic repos, prioritize:

package structure
clear CLI/scripts
configs
environment lock or setup docs
tests for structural invariants
reproducibility commands
data provenance
paper/proposal placement
wiki/source summaries