Happier Release Validation Review
Testing & Qualityhappier-release-validation-reviewHappier Release Validation Review is an Agent Skill for testing & quality published in the happier-dev/happier repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Review a completed Happier release-validation worktree before any preview promotion. Audits validation fixes, diffs, evidence, lane completion, unresolved risks, and dry-run output. Read-only by default and never releases.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/happier-dev/happier/blob/HEAD/skills/happier-release-validation-review/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/happier-release-validation-review, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Happier Release Validation Review
Use this skill after happier-release-validation finishes and before any release or preview promotion.
Mission
Act as a skeptical release-candidate reviewer. Verify that the validation branch changes are correct, necessary, root-cause-oriented, well-tested, and supported by evidence. Do not promote or release.
Inputs
- Validation worktree path
- Live workspace under
.project/reviews/<date>-v<version>-release-validation/ TRACKING.md,PLAN.md,LEDGER.md, lane docs, evidence directorygit difffor the validation branch- final custom checks result
- local release dry-run output
Process
- Re-read
AGENTS.md. - Read
references/review-rubric.md. - In the validation worktree, read
TRACKING.md,PLAN.md, andLEDGER.md. - Verify every completed lane has evidence for its claim.
- Review every code change made during validation with normal code-review severity.
- Confirm tests follow TDD expectations where behavior changed.
- Confirm no workaround fixes, hidden skips, destructive cleanup, or release side effects happened.
- Review
TRACKING.md#Process Feedbackand classify each item asback-port now,back-port later, orignore. - Produce a concise sign-off packet.
Verdicts
APPROVE_FOR_PREVIEW_PROMOTION: evidence and diffs support promotion.NEEDS_FIXES: specific issues must be fixed before promotion.NEEDS_MORE_EVIDENCE: claims may be true but evidence is insufficient.BLOCKED: cannot review because required inputs are missing.
This skill is read-only by default. If fixes are required, ask before editing or direct the user back to happier-release-validation for another fix/validation loop.