Standardizes the definition of 'ready-to-ship' via automated smoke tests and release documentation.
Install
mkdir -p .claude/skills/release-readiness-harness && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14359" && unzip -o skill.zip -d .claude/skills/release-readiness-harness && rm skill.zipInstalls to .claude/skills/release-readiness-harness
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Define and validate what ready-to-ship means beyond tests passing. Use when a repo needs release checklists, smoke tests, rollback plans, changelog/versioning guidance, deployment verification, or scripts/smoke-test.Key capabilities
- →Define release readiness criteria
- →Add release assets like checklists and rollback plans
- →Create smoke test scripts for quick verification
- →Coordinate with CI/CD workflows for deployment gates
- →Confirm rollback steps are concrete
- →Validate release docs cite validation commands
How it works
This skill defines and validates release readiness by creating checklists, smoke tests, and rollback plans to ensure deployment safety beyond just passing tests.
Inputs & outputs
When to use release-readiness-harness
- →Create a release checklist
- →Add a smoke test script
- →Draft a rollback plan
About this skill
Release Readiness Harness
Purpose
Prevent agents from treating a passing test suite as the whole release decision.
Inspect First
- release docs, CI/CD workflows, deployment config, smoke tests, migrations, changelog, version files, rollback docs, and observability diagnostics
Procedure
-
Define readiness.
- Full validation evidence from
./scripts/validateor documented equivalent. - Fast smoke tests that prove the release/runtime can start and answer a minimal health or user-flow check.
- Migration status.
- Rollback plan.
- Monitoring or diagnostics.
- Known risks.
- Full validation evidence from
-
Add release assets.
docs/release/checklist.mddocs/release/rollback.mdscripts/smoke-testwhere feasible; keep it fast and runtime/deployment-focused, not a default alias for full./scripts/validate.- Select a stack-aware smoke pattern when useful:
- web app: request the base URL or one minimal browser smoke path.
- API service: request
/healthor the configured health endpoint. - database-backed app: check database readiness plus migration status.
- library/package: run a fast import/build sanity check.
CHANGELOG.mdwhen the project uses changelogs or the user asks.
-
Wire checks.
- Coordinate with
ci-cd-harnessfor deployment gates. - Coordinate with
migration-and-schema-harnessfor migration risk. - Coordinate with
termination-gatekeeperso release readiness is not claimed before task completion evidence exists.
- Coordinate with
Validation
- Run
./scripts/smoke-testwhen present. - Run or cite full
./scripts/validateseparately from smoke evidence. - Confirm rollback steps are concrete.
- Confirm release docs cite validation commands.
Completion Criteria
- A release has explicit readiness, smoke, rollback, and verification criteria.
When not to use it
- →When a passing test suite is considered sufficient for release
- →When the project does not require formal release processes
- →When the task is solely about running existing tests
Limitations
- →The skill does not execute full validation evidence by default.
- →The skill does not replace full `./scripts/validate` with smoke tests.
- →The skill does not automatically generate changelogs unless requested.
How it compares
This skill enforces a structured release harness with explicit verification steps, unlike a simple test-passing approach that might overlook critical deployment risks.
Compared to similar skills
release-readiness-harness side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| release-readiness-harness (this skill) | 0 | 2mo | No flags | Intermediate |
| agent-production-validator | 3 | 6mo | Review | Advanced |
| validate-delivery | 1 | 5mo | Review | Beginner |
| release-testing | 1 | 1mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
agent-production-validator
ruvnet
Agent skill for production-validator - invoke with $agent-production-validator
validate-delivery
avifenesh
Use when validating task completion before shipping. Runs tests, build, and requirement checks. Returns pass/fail with fix instructions.
release-testing
mono
Run integration tests to verify SkiaSharp NuGet packages work correctly before publishing. Use when user asks to: - Test/verify packages before release - Run integration tests - Test on specific device (iPad, iPhone, Android emulator, Mac, Windows) - Verify SkiaSharp rendering works - Check if packages are ready for publishing - Run smoke/console/blazor/maui tests - Continue with release - Test version X Triggers: "test the release", "verify packages", "run tests on iPad", "check ios tests", "test mac catalyst", "run android tests", "continue", "test 3.119.2-preview.2".
documenso-ci-integration
jeremylongshore
Configure CI/CD pipelines for Documenso integrations. Use when setting up automated testing, deployment pipelines, or continuous integration for Documenso projects. Trigger with phrases like "documenso CI", "documenso GitHub Actions", "documenso pipeline", "documenso automated testing".
smoke-check
hoatv2211
Run core path smoke validation before QA handoff or merge.
aidlc-build
aws-samples
Final integration build and test verification. Validates that implemented code compiles, passes all test suites, and meets quality gates before deployment.