Release Check

What Is Release Check?

Release Check is a high-stakes pre-release verification skill designed for engineering teams prioritizing robust quality assurance before deploying software into production environments. Integrated with the Centinela (QA) agent, Release Check consolidates critical validation steps into a single, automated workflow. By orchestrating checks across documentation, technical debt, testing, code quality, and security, this skill acts as the final safeguard—ensuring that only rigorously vetted builds are released. Release Check is especially valuable when tagging production versions, acting as the ultimate quality gate after feature development and code reviews are complete.

Why Use Release Check?

Releasing software introduces risk. Minor oversights in documentation, testing, or security can result in expensive production incidents, eroding user trust and causing operational headaches. Manual pre-release reviews are time-consuming and error-prone, especially as projects grow in complexity.

Release Check addresses these challenges by providing:

• Standardization: Enforces a consistent, repeatable checklist across every release candidate.
• Comprehensiveness: Validates not just code, but also documentation, technical debt, and security.
• Automation: Delegates verification to the Centinela QA agent, reducing human error and freeing up engineering time.
• Actionable Output: Automatically generates a detailed release assessment report with a clear verdict—either “READY FOR RELEASE” or “BLOCKED” with reasons.
• Auditability: Stores release assessments in your codebase for future reference and compliance needs.

By using Release Check, teams elevate their release process, minimizing the risk of shipping incomplete, insecure, or low-quality software.

How to Get Started

Setting up Release Check is straightforward if your project is already using skills compatible with Claude Code and the Centinela QA agent.

1. Install the Skill
   Add the release-check skill to your project, referencing the official repository for up-to-date instructions.

2. Prepare Your Project
   Ensure the following artifacts are present in your repository:

   • Up-to-date CHANGELOG
   • Documentation and specifications
   • Clearly tracked technical debt (e.g., TECH_DEBT file)
   • Comprehensive test suites

3. Run Release Check
   Use the release check command with the target version:

   bash

   /release-check v1.2.0

   The Centinela agent will perform all verification steps and generate a report in docs/reviews/release-check-v1.2.0.md.

4. Review Results
   Examine the generated report. If the release is blocked, address the documented issues and re-run the check.

Key Features

Release Check offers a structured process encompassing the following phases:

1. SIGN IN Checklist
   Initial verification step to authenticate and ensure proper context for the release candidate.

2. TIME OUT 1 — Documentation and Debt Check

   • Verifies CHANGELOG accuracy and completeness.
   • Checks for outstanding technical debt in tracked files (e.g., TECH_DEBT).
   • Ensures specs and user-facing documentation are current.

3. TIME OUT 2 — Testing and Quality Gate

   • Runs all available test suites (unit, integration, end-to-end).
   • Performs automated code health scans.
   • Validates code against established quality gate metrics.

4. TIME OUT 3 — Security and Release Gate

   • Conducts security audits for dependencies, secrets, and vulnerabilities.
   • Ensures all critical security checks pass.
   • Confirms final release readiness.

5. Automated Assessment Generation

   • Writes a detailed release assessment to docs/reviews/release-check-{version}.md.
   • Provides a verdict: READY FOR RELEASE or BLOCKED, with specific blocking reasons.

Example Output (simplified):

## Release Assessment: v2.0.0

## Documentation & Debt
- CHANGELOG: complete
- TECH_DEBT: 0 critical, 3 minor
- Docs: up-to-date

## Testing & Quality
- All tests passed
- Quality gates met

## Security
- Security audit: no critical issues

## Verdict
READY FOR RELEASE

Best Practices

• Integrate Early: Adopt Release Check before your first production release to build a culture of quality from the start.
• Automate Invocations: Configure your CI/CD pipeline to trigger /release-check automatically before tagging or deploying new versions.
• Iterate on Failures: Treat blocked releases as learning opportunities—use detailed feedback to improve your code, tests, and documentation.
• Keep Artifacts Current: Regularly update your CHANGELOG, technical debt tracker, and documentation to prevent last-minute blockers.
• Review Reports: Always review the generated assessment for actionable feedback, even if the verdict is “READY FOR RELEASE.”

Important Notes

• Skill Prerequisite: Release Check requires the Centinela (QA) agent to function, as it delegates verification tasks to this quality assurance agent.
• Blocking Is Protective: A “BLOCKED” verdict prevents flawed releases from reaching users. Address all issues before attempting a new release.
• Customization: While the default checklist is comprehensive, you can tailor the workflow to fit your organization’s specific quality gates and documentation standards via skill configuration.
• Audit Trail: Every assessment is saved under docs/reviews/, providing an auditable trail of release decisions for compliance and retrospectives.
• Not a Substitute for Peer Review: Release Check is a complement to, not a replacement for, rigorous code review and engineering judgment.

By incorporating Release Check into your release workflow, you ensure that every deployment is backed by a thorough, automated, and repeatable verification process—drastically reducing the risk of post-release defects and security incidents.