HSquared.jl

Close a hsquared or HSquared.jl task with repo-visible evidence. Use after meaningful docs, code, tests, CI, coordination, GitHub issue, or public-readiness work.

Review the future bridge from hsquared R calls to HSquared.jl. Use for marshalling, JuliaCall or other bridge choices, result-shape parity, engine controls, and R placeholder/error wording.

Review the HSquared.jl engine contract for input payloads, result shape, storage policy, diagnostics, controls, and numerical assumptions. Use when changing docs or code at the R-Julia boundary or Julia engine API.

Review hsquared formula, covariance, and relationship grammar. Use when adding or changing R syntax, Julia formula equivalents, unsupported-syntax errors, examples, docs, or the R-Julia model specification.

Rehydrate the hsquared or HSquared.jl project before substantial work. Use when resuming a thread, starting a new slice, recovering after interruption, checking coordination state, or preparing edits that depend on repo, CI, roadmap, or twin-lane status.

Dispatch hsquared work across coordinator, R, and Julia lanes. Use before starting a substantial slice, spawning agents, steering the Julia twin thread, touching shared docs, or deciding which named review lenses are active.

Review pedigree validation, ID recoding, sorting, founder handling, unknown parents, and sparse Ainv construction for hsquared and HSquared.jl. Use before claiming pedigree or animal-model support.

Review hsquared README, design docs, vignettes, issue text, and release prose for reader-first, concrete, honest wording. Use when public or long-form prose changes.

Scout quantitative-genetic packages, papers, and software before hsquared design or claim changes. Use for ASReml, MCMCglmm, sommer, JWAS, BLUPF90, DMU, WOMBAT, AGHmatrix, nadiv, XSim, G matrices, AI-REML, APY, pedigree, genomic, and inheritance-system comparisons.

Audit hsquared public claims before making repos public, updating README/DESCRIPTION, opening issues, adding badges, or publishing docs. Use to separate implemented, partial, planned, blocked, and missing capabilities.

Review hsquared validation evidence, benchmarks, simulation studies, Mrode examples, comparator runs, and validation debt rows. Use before moving a capability from planned or partial to covered.