Code review
AuraScore 77/100

Bioinformatics Pipeline Code Review and Validation Plan

Establish a peer-review workflow and quality assurance plan for high-throughput genomic data processing pipelines.

Apply this template when structuring code review standards for complex Nextflow, WDL, or Snakemake pipelines. It focuses on deterministic reproducibility, container hygiene, and high-performance compute resource handling.

Template

Role: Senior Bioinformatics DevOps Engineer specializing in scalable workflow engines, genomic data pipelines, and GxP computational reproducibility.

Context

  • Workflow Framework: {{pipeline_framework}}
  • Sequencing Assay Type: {{sequencing_assay_type}}
  • Computational Infrastructure: {{compute_cluster_environment}}
  • Primary Review Challenge: {{primary_review_bottleneck}}
  • Reproducibility Benchmark: {{reproducibility_benchmark}}
  • Data Governance Tier: {{data_governance_tier}}

Task

Design a structured code review workflow and validation plan that eliminates {{primary_review_bottleneck}}, enforces deterministic execution across {{compute_cluster_environment}}, and guarantees compliance with {{data_governance_tier}} standards for the {{sequencing_assay_type}} pipeline.

Method

  1. Evaluate current pull-request bottlenecks in the {{pipeline_framework}} repository and define clear triage criteria.
  2. Create module-level code review requirements focusing on container pinning, software version tagging, and deterministic random seeds.
  3. Establish memory, CPU, and disk dynamic allocation review rules tailored for {{compute_cluster_environment}} job management.
  4. Design intermediate file caching and I/O optimization inspection gates to prevent cloud storage cost overruns.
  5. Define synthetic reference dataset verification tests matching {{sequencing_assay_type}} requirements for all PR submissions.
  6. Formulate a variant-calling output concordance benchmark against {{reproducibility_benchmark}} to validate algorithm parity.
  7. Construct a peer-review scorecard integrating bioinformatics SME validation, infrastructure review, and governance checks.

Constraints

  • MUST require container digest pinning (SHA256) for every module change during review.
  • MUST NOT approve pipeline revisions that fail the concordance threshold set by {{reproducibility_benchmark}}.
  • Keep review checklist actionable and constrained to bioinformatic workflow logic and infrastructure definitions.
  • Align all data staging review points with {{data_governance_tier}} access controls.

Output format

  1. Review Process Diagnostic & Bottleneck Remediation (150 words)
  2. Pipeline Code Review Checklist (6 categories: Containers, HPC Config, I/O, Reproducibility, Style, Security)
  3. Pull Request Validation Workflow (Step-by-step CI/CD and human review gates)
  4. Reproducibility & Governance Sign-Off Scorecard (Tabular template with pass/fail criteria)

Self-review

  • Verify that the plan specifically resolves {{primary_review_bottleneck}} without introducing manual delays.
  • Ensure all container and resource allocation checks reflect the constraints of {{compute_cluster_environment}}.
  • Check that the validation criteria enforce the exact assay expectations of {{sequencing_assay_type}}.
AuraScore breakdown
77/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering8/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

developers
developers-code-review
healthcare-life-sciences
bioinformatics
genomics
nextflow