Use before claiming Codewhale release work is done: a pointer to docs/RELEASE_CHECKLIST.md for the gates and to cw-dogfood for the manual QA targets.
75%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./docs/skills/codew-release-qa-sweep/SKILL.mdNo sweep, no "done". This skill owns nothing itself; it points at the two places that do.
docs/RELEASE_CHECKLIST.md from the
canonical checkout on main (docs/RELEASE_RUNBOOK.md for the tools behind
it). Native builds go through scripts/dev-cargo.sh / scripts/dev-test.sh
(cw-gates). Every push to main runs full hosted
CI; the release step dispatches CI and release-candidate.yml again on the
frozen candidate commit.Exercise each in a real terminal and record what you saw. The scenarios are described in cw-dogfood; the refs are the reports that motivated them.
Each command, pass or fail, and the salient output line (test counts, the
--version string, the check-versions.sh verdict). For manual QA, what you
observed per target, citing the ref. Name what you skipped (for example, no
display for TUI QA) rather than implying coverage you do not have.
Hmbown/Codewhale
3e1359f
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.