prepare-a-bioconductor-ready-package

Audit and mature R packages for Bioconductor submission readiness and ecosystem interoperability.

1|Updated Aug 11, 2026
One-click install
npx skills add https://github.com/0xMuluh/package-development-skills --skill prepare-a-bioconductor-ready-package-0xmuluh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prepare-a-bioconductor-ready-package
Source: https://github.com/0xMuluh/package-development-skills/tree/main/prepare-a-bioconductor-ready-package
Command: npx skills add https://github.com/0xMuluh/package-development-skills --skill prepare-a-bioconductor-ready-package-0xmuluh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Preparing an R package for Bioconductor submission involves many evolving requirements: DESCRIPTION metadata, biocViews, NAMESPACE hygiene, executable vignettes, data provenance, size limits, and passing R CMD check plus BiocCheck in the current devel environment. This Skill provides a structured audit and maturation workflow so packages meet official Bioconductor expectations without one giant redesign PR. ## Core Features & Use Cases - Phased Readiness Audit: Walks through package identity, interoperability, DESCRIPTION, NAMESPACE, R code, documentation, vignettes, tests, data provenance, repository hygiene, and resource limits. - Ecosystem-First Philosophy: Enforces reuse of established Bioconductor classes (SummarizedExperiment, SingleCellExperiment, GRanges), generics, and public APIs instead of parallel package-specific machinery. - Semantic PR Decomposition: Classifies findings into submission blockers, correctness issues, documentation gaps, and optional improvements so readiness work ships as small reviewable changes. - Use Case: A maintainer with an existing R package using private dependency APIs and no vignette runs this audit to produce a submission readiness report, then fixes blockers in separate PRs before validating with R CMD build, R CMD check, and BiocCheck in the current devel environment. ## Quick Start Audit my R package for Bioconductor submission readiness and produce a report of blockers and recommended fixes.

Frequently Asked Questions about prepare-a-bioconductor-ready-package

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

FAQPage Schema
How do I prepare an R package for Bioconductor submission?▼

Audit the package against current official Bioconductor development guidance: verify DESCRIPTION metadata and biocViews, reuse existing Bioconductor classes and generics, add an executable vignette and behavioral tests, document data provenance, then validate with R CMD build, R CMD check, and BiocCheck in the current devel environment.

What version number does a new Bioconductor package need?▼

New Bioconductor submissions use a pre-release version such as 0.99.0 according to official guidance at the time of writing. Always re-check the current Bioconductor versioning documentation before submission because requirements evolve.

Can a Bioconductor package depend on GitHub-only packages?▼

No. Bioconductor packages must depend on packages available through supported Bioconductor or CRAN repositories. GitHub-only runtime dependencies, unsupported Remotes fields, and arbitrary source URLs must be resolved before submission.

Why does BiocCheck fail on my R package?▼

BiocCheck flags issues like direct slot access, private ::: API usage, missing biocViews, non-executable vignettes, oversized files, and missing documentation. Classify each finding semantically and fix the underlying issue rather than suppressing the check.

Should I fix all Bioconductor readiness issues in one PR?▼

No. Classify findings into submission blockers, correctness issues, documentation gaps, and optional improvements, then create small semantic PRs. Combining rewrites, vignettes, API renames, and reformats into one PR hides architectural problems and complicates review.