Release Check
Testing & Qualityrelease-checkRelease Check is an Agent Skill for testing & quality published in the davepoon/buildwithclaude repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Pre-release verification checklist. Validates features, tests, docs, security, and quality gates before shipping. Delegates to the Centinela (QA) agent.
QUICK START
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.
Prompt to paste
Inspect the Agent Skill at https://github.com/davepoon/buildwithclaude/blob/HEAD/plugins/agent-triforce/skills/release-check/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/release-check, 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.
Release Check
Runs pre-release verification using the Centinela (QA) agent. This is the highest-stakes checklist in the system.
When to Use This Skill
- Before any release to production
- Before tagging a version
- As a final quality gate after all features are implemented and reviewed
What This Skill Does
- Runs the SIGN IN checklist
- TIME OUT 1 — Documentation and Debt Check: verifies CHANGELOG, TECH_DEBT, specs, and docs
- TIME OUT 2 — Testing and Quality Gate: runs all tests, code health scan, quality verification
- TIME OUT 3 — Security and Release Gate: runs security audit, security verification, release readiness
- Writes release assessment to
docs/reviews/release-check-{version}.md - Issues final verdict: READY FOR RELEASE or BLOCKED (with specific reasons)
How to Use
Basic Usage
/release-check v1.2.0
Example
User: /release-check v2.0.0
Output: A release assessment at docs/reviews/release-check-v2.0.0.md with:
- Documentation completeness check
- Test results and quality gate status
- Security audit summary
- Final verdict with specific blocking reasons if any
Tips
- This is the last line of defense before code reaches users
- A blocked release here prevents issues from reaching production
- Three TIME OUT checkpoints cover docs, quality, and security independently