Run any Skill in Manus with one click

Get Started

release-readiness-review

Stars0

Forks0

UpdatedJuly 12, 2026 at 11:54

Review freqTLS before a public, CRAN, GitHub, or internal release.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

itchyshin

itchyshin/freqTLS

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Data ScientistsComputer and Mathematical Occupations·SOC 15-2051

SKILL.md

readonly

name	release-readiness-review
description	Review freqTLS before a public, CRAN, GitHub, or internal release.

Release Readiness Review

Use this skill before public releases, GitHub releases, or version tags. Grace leads; Rose audits claims; Pat and Fisher hold the Definition-of-Done gate.

Required Checks

Confirm the current branch and a clean working tree.
Review NEWS.md, README.Rmd (and the rendered README.md), ROADMAP.md, docs/dev-log/known-limitations.md, docs/design/46-capability-matrix.md, and the _pkgdown.yml navigation.
Run the package checks appropriate to the release:
- devtools::document()
- devtools::test()
- devtools::check()
- pkgdown::check_pkgdown() and pkgdown::build_site()
Check examples and vignettes for unsupported syntax, stale claims, or any "posterior"/"credible" language describing a freqTLS interval.
Check dependency versions and platform risks; confirm the normal-Suggests CI matrix covers Ubuntu R release/devel, Windows R release, and macOS R release, and remains Stan-free.
Confirm the benchmark cache provenance is current and the article reads the cache (no live Stan in CI). Restrict equivalence claims to the matched relative-threshold, constant-shape model fits; identify the classical two-stage comparator as an absolute-LT50 approximation.
Audit every installed data/extdata component against docs/design/47-data-license-ledger.md, R/data.R, inst/COPYRIGHTS, and inst/CITATION. Confirm snow-gum remains labelled CC BY-NC 4.0 and that snow-gum, Kristineberg, or any other permission-pending asset is absent from the source tarball unless written redistribution authority is recorded.
Confirm Pieter A. Arnold, Patrice Pottier, and Daniel W. A. Noble have explicitly agreed to their aut roles before public release or CRAN upload.
Build one exact source tarball, record its checksum and inventory, and run R CMD check --as-cran on that file with normal Suggests. Require zero errors and warnings and explain every NOTE.
Before CRAN upload, require the candidate commit's GitHub platform matrix, win-builder R-devel, R-hub Linux/clang, and independent Grace/Rose/Pat completion verdicts. Record skipped checks and residual risks in the check log without describing pending gates as passed.

Release Questions

What is implemented, documented, and tested?
What is planned but not implemented (the 0.1.0 non-goals)?
What should users avoid (weakly identified designs; extrapolated CTmax)?
What changed since the previous release?
What would make the release embarrassing if found tomorrow?

More from this repository

same repository

benchmark-vs-bayestls-audit

itchyshin/freqTLS

Audit the freqTLS-versus-bayesTLS benchmark for a fair configuration, sound cache provenance, and the correct R-SHRIMP data rebuild.

2026-07-120

figure-visual-audit

itchyshin/freqTLS

Audit and improve freqTLS figures, galleries, pkgdown articles, and ggplot recipes, enforcing the Confidence-Eye uncertainty contract, before Florence, Rose, Pat, Fisher, and Grace call a figure done.

2026-07-120

add-simulation-test

itchyshin/freqTLS

Add simulation-based parameter-recovery tests for freqTLS models.

2026-06-240

after-task-audit

itchyshin/freqTLS

Audit a completed freqTLS task or phase before closing it, checking implementation, equations, examples, tests, docs, pkgdown, roadmap, NEWS, the capability matrix, known limitations, stale wording, and after-task reporting.

2026-06-240

profile-ci-review

itchyshin/freqTLS

Review freqTLS profile-likelihood confidence intervals for correctness, equivariance, chi-square calibration, and honest open/boundary/multimodal handling.

2026-06-240

prose-style-review

itchyshin/freqTLS

Review and improve freqTLS prose in README files, vignettes, pkgdown articles, after-task reports, release notes, design docs, and manuscript-style text for clarity, concrete claims, stable terminology, citations, and reader fit.

2026-06-240

Release Readiness Review

Use this skill before public releases, GitHub releases, or version tags. Grace leads; Rose audits claims; Pat and Fisher hold the Definition-of-Done gate.

Required Checks

Confirm the current branch and a clean working tree.

Review NEWS.md, README.Rmd (and the rendered README.md), ROADMAP.md, docs/dev-log/known-limitations.md, docs/design/46-capability-matrix.md, and the _pkgdown.yml navigation.

Run the package checks appropriate to the release:

devtools::document()
devtools::test()
devtools::check()
pkgdown::check_pkgdown() and pkgdown::build_site()

Check examples and vignettes for unsupported syntax, stale claims, or any "posterior"/"credible" language describing a freqTLS interval.

Check dependency versions and platform risks; confirm the normal-Suggests CI matrix covers Ubuntu R release/devel, Windows R release, and macOS R release, and remains Stan-free.

Confirm the benchmark cache provenance is current and the article reads the cache (no live Stan in CI). Restrict equivalence claims to the matched relative-threshold, constant-shape model fits; identify the classical two-stage comparator as an absolute-LT50 approximation.

Audit every installed data/extdata component against docs/design/47-data-license-ledger.md, R/data.R, inst/COPYRIGHTS, and inst/CITATION. Confirm snow-gum remains labelled CC BY-NC 4.0 and that snow-gum, Kristineberg, or any other permission-pending asset is absent from the source tarball unless written redistribution authority is recorded.

Confirm Pieter A. Arnold, Patrice Pottier, and Daniel W. A. Noble have explicitly agreed to their aut roles before public release or CRAN upload.

Build one exact source tarball, record its checksum and inventory, and run R CMD check --as-cran on that file with normal Suggests. Require zero errors and warnings and explain every NOTE.

Before CRAN upload, require the candidate commit's GitHub platform matrix, win-builder R-devel, R-hub Linux/clang, and independent Grace/Rose/Pat completion verdicts. Record skipped checks and residual risks in the check log without describing pending gates as passed.

Release Questions

What is implemented, documented, and tested?

What is planned but not implemented (the 0.1.0 non-goals)?

What should users avoid (weakly identified designs; extrapolated CTmax)?

What changed since the previous release?

What would make the release embarrassing if found tomorrow?