verification-and-release

Verification and Release

Issue a release decision only from evidence proportional to consequence, novelty, and reversibility.

Trigger boundary

Use this skill for:

• designing a verification plan from a diff, migration, or release candidate;
• auditing CI/test evidence and identifying material gaps;
• deciding READY, CONDITIONAL, or BLOCKED for a release;
• defining rollout, monitoring, rollback, and post-release checks.

Do not trigger for:

• implementing product behavior or writing the initial feature tests;
• investigating why a test or production symptom fails—use debugging-investigator;
• executing an upgrade—use codebase-evolution-controller;
• reviewing a tiny local edit when no release decision or broader evidence strategy is requested.

Required inputs

Collect or explicitly mark unavailable:

1. integrated diff or release candidate identifier and repository state;
2. intended behavior, acceptance criteria, and affected users/consumers;
3. architecture/change-impact evidence and risk-sensitive surfaces;
4. CI runs, local checks, coverage or test map, and known baseline failures;
5. deployment topology, feature flags, migrations, observability, and rollback mechanism;
6. security, privacy, compliance, platform, and compatibility constraints;
7. release scope, cohort, timing, and responsible owner.

A list of commands without the exact artifact/ref and result is not release evidence.

Safety baseline

• Inspect current worktree and candidate identity before running checks.
• Do not discard, clean, stash, rewrite, or auto-fix user work.
• Do not mark a check passed when it was skipped, filtered, flaky, retried to green without analysis, or run against a different revision.
• Do not expose secrets in logs, screenshots, or evidence bundles.
• Do not perform production deployment or rollback merely because this skill recommends it; use the project's authorized release mechanism and owner.
• Treat irreversible schema/data changes as release blockers until restore or forward-recovery evidence exists.