Menu
Review Nextflow DSL 2 implementations against spec acceptance tests. References implementation-principles, nextflow-conventions, testing-principles, and agent-conduct.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Orchestrates standalone or caller-batched bug fixes via implementor and reviewer subagents using TDD. Handles bugs and verified review findings sequentially, tracks them in a dated checklist, and commits each fix without disrupting a surrounding PR-resolution batch.
Resolve GitHub PR review comments from humans and Copilot, including reviews already auto-requested or in progress. Use for verified comment resolution, sequential bugfix batching, one-push CI/Copilot cycles, and SHA-aware waits that avoid stale-event loops.
Shared conventions for Go projects. Copyright boilerplate, code quality, GoConvey testing, architecture, and commands. Referenced by go-implementor, go-reviewer, and workflow skills.
Go TDD implementation workflow. References implementation-principles, go-conventions, testing-principles, and agent-conduct.
Review Go implementations against spec acceptance tests. References implementation-principles, go-conventions, testing-principles, and agent-conduct.
Shared cross-language delivery workflow and guidance for implementing the simplest sufficient solution, maximizing reuse of existing code, and avoiding speculative abstractions, dependencies, and refactors. Use when implementing or reviewing code in any language.
| name | nextflow-reviewer |
| description | Review Nextflow DSL 2 implementations against spec acceptance tests. References implementation-principles, nextflow-conventions, testing-principles, and agent-conduct. |
| context | fork |
Read and follow agent-conduct, implementation-principles, testing-principles, and nextflow-conventions before starting.
You are a review subagent with clean context. Independently verify that code meets the spec and quality standards.
For each item:
nf-test test modules/local/<tool>/tests/main.nf.test
Run for every modified module. All must pass. Then run pipeline-level tests:
nf-test test
Every spec.md acceptance test must have a corresponding nf-test. Reject missing, stubbed (unless data-size justified), circumvented, or hardcoded-result tests. Apply the testing-principles review rule.
modules/local/<tool>/main.nf.tests/main.nf.test with snapshot assertions.meta map pattern: tuple val(meta), path(...).emit:), not positional.tag, label on every process.modules/nf-core/.versions.yml with tool version(s).versions.yml aggregated in the main workflow.nextflow.config: default params, profile includes.conf/base.config: resource labels (process_low, _medium, _high).conf/modules.config: publishDir and ext.args per module.docker, singularity, test.docs/usage.md: params, input format, run examples.docs/output.md: all output files described.README.md: overview, quick start.nf-core pipelines lint
No errors for modified files.