메뉴
Nextflow DSL 2 TDD implementation workflow. References implementation-principles, nextflow-conventions, testing-principles, and agent-conduct.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
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-implementor |
| description | Nextflow DSL 2 TDD implementation workflow. 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.
modules/local/<tool>/tests/main.nf.test.nf-test test modules/local/<tool>/tests/main.nf.testversions.yml with tool version(s).nf-core pipelines lint and fix issues.Split each tool/function into its own module under modules/local/<tool>/main.nf
with a corresponding tests/main.nf.test. One process per file, one test file
per module.
Before creating a local module, check nf-core:
nf-core modules list remote | grep <tool>
If a suitable module exists, install it (nf-core modules install <tool>)
instead of writing a local one. Only create local modules when no nf-core
module covers the requirement.
For local modules without nf-core equivalents, find open-source containers:
Specify both docker and singularity container paths.
After all modules pass, ensure:
nextflow.config has default params.conf/base.config has resource labels.conf/modules.config has publishDir directives.docker, singularity, test.versions.yml.docs/usage.md and docs/output.md are written for end-users.