OpenParable
Skip to content
← Back to skills

Happier Release Validation Review

Testing & Quality
happier-release-validation-review

Happier 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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
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 directory
  • git diff for the validation branch
  • final custom checks result
  • local release dry-run output

Process

  1. Re-read AGENTS.md.
  2. Read references/review-rubric.md.
  3. In the validation worktree, read TRACKING.md, PLAN.md, and LEDGER.md.
  4. Verify every completed lane has evidence for its claim.
  5. Review every code change made during validation with normal code-review severity.
  6. Confirm tests follow TDD expectations where behavior changed.
  7. Confirm no workaround fixes, hidden skips, destructive cleanup, or release side effects happened.
  8. Review TRACKING.md#Process Feedback and classify each item as back-port now, back-port later, or ignore.
  9. 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.