repro-enforcer

Export bioinformatics analyses as reproducible bundles with Conda, containers, and pipelines.

1.1k|238|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/ClawBio/ClawBio --skill repro-enforcer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repro-enforcer
Source: https://github.com/ClawBio/ClawBio/tree/main/skills/repro-enforcer
Command: npx skills add https://github.com/ClawBio/ClawBio --skill repro-enforcer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many bioinformatics analyses are difficult to reproduce because runtime environments, container definitions, and workflow implementations are not captured or versioned consistently. Repro Enforcer automates exporting an analysis into a self-contained reproducibility bundle so collaborators and reviewers can rebuild the exact runtime, pipeline, and artifacts.

Core Features & Use Cases

  • Conda Export: Capture and pin the current Conda environment into an environment.yml for deterministic package versions.
  • Container Definitions: Generate Singularity .def files and Dockerfiles/docker-compose manifests to build portable containers.
  • Workflow Conversion: Translate sequences of shell commands into Nextflow DSL2 pipelines or Snakemake workflows for scalable execution.
  • Integrity & Documentation: Produce SHA-256 checksum manifests and a human-readable README with reproduction instructions.
  • Use Case: Package an ad-hoc analysis into a reproducible artifact for publication, peer review, or long-term archiving.

Quick Start

Use the repro-enforcer skill to export my analysis folder as a reproducible bundle with a pinned Conda environment, a Singularity definition, and a Nextflow pipeline.

Frequently Asked Questions about repro-enforcer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I export a bioinformatics analysis as a reproducible bundle with a pinned Conda environment?

To export a bioinformatics analysis as a reproducible bundle, you capture and pin the current Conda environment into an environment.yml file for deterministic package versions. This ensures your runtime environment is completely portable and version-controlled for collaborators.

What is the best way to convert ad-hoc shell commands into a Nextflow or Snakemake pipeline?

Converting ad-hoc shell commands into a Nextflow or Snakemake pipeline is done by translating command sequences into scalable workflow definitions. This workflow conversion allows ad-hoc analyses to be executed as structured Nextflow DSL2 pipelines or Snakemake workflows.

Do I need checksum manifests and reproduction instructions for a portable bioinformatics workflow?

Checksum manifests and reproduction instructions are needed to verify integrity and guide rebuilding a portable bioinformatics workflow. Producing SHA-256 checksums and a human-readable README ensures your analysis artifacts remain verifiable and reproducible for publication.

Can I use this approach to package an ad-hoc analysis for peer review and long-term archiving?

Yes, you can package an ad-hoc analysis for peer review and long-term archiving by exporting it into a self-contained reproducibility bundle. This bundle captures the environment, containers, pipelines, and checksums so reviewers can rebuild the exact runtime and artifacts.

Does this reproducibility bundle approach work with both Singularity and Docker definitions?

Yes, the reproducibility bundle approach works with both Singularity and Docker definitions. It generates Singularity .def files and Dockerfiles alongside docker-compose manifests to ensure your containerized bioinformatics analysis is portable across different HPC and cloud environments.