Final Release Review
Automates final release checks, verifying deployment readiness and identifying potential issues before production launch.
Install on your platform
We auto-selected Claude Code based on this skill’s supported platforms.
Run in terminal (recommended)
claude mcp add final-release-review npx -- -y @trustedskills/final-release-review
Or manually add to ~/.claude/settings.json
{
"mcpServers": {
"final-release-review": {
"command": "npx",
"args": [
"-y",
"@trustedskills/final-release-review"
]
}
}
}Requires Claude Code (claude CLI). Run claude --version to verify your install.
About This Skill
What it does
The Final Release Review skill automates checks for release candidates, ensuring deployment readiness and identifying potential issues before a production launch. It fetches remote tags, compares changes between a previous release tag (BASE_TAG) and the latest commit (TARGET), and analyzes this diff for breaking changes, regressions, bugs, or risks. The goal is to provide a stable and actionable review that avoids false positives when blocking a release.
When to use it
- Validating a new release candidate before production deployment.
- Inspecting changes between the previous released version and the latest commit on
origin/main. - Identifying potential breaking changes, regressions, or security vulnerabilities introduced in the new release.
- Ensuring that all necessary checks are completed before approving a release for shipment.
Key capabilities
- Fetches remote tags to identify the BASE_TAG (previous release).
- Compares code changes between BASE_TAG and TARGET commit using
git diffandgit log. - Analyzes changes for breaking changes, regressions, data loss, or security impacts.
- Provides a deterministic gate policy: GREEN LIGHT TO SHIP unless specific blocking triggers are met.
- Requires concrete evidence and actionable steps to issue a BLOCKED call.
Example prompts
- "Run the final release review on the latest commit."
- "Perform a final release check comparing tag v1.0.0 with origin/main."
- "Review changes between the previous release and the current version, focusing on potential security risks."
Tips & gotchas
- Ensure the repository is at the root directory:
path-to-workspace/openai-agents-python. - The skill assumes that the target commit (
origin/main) has already passed code change verification in CI. - Avoid issuing a BLOCKED call without concrete evidence and clear unblock actions; prioritize GREEN LIGHT TO SHIP with targeted validation follow-ups when evidence is incomplete.
Tags
TrustedSkills Verification
Unlike other registries that point to live repositories, TrustedSkills pins every skill to a verified commit hash. This protects you from malicious updates — what you install today is exactly what was reviewed and verified.
Security Audits
| Gen Agent Trust Hub | Pass |
| Socket | Pass |
| Snyk | Pass |
🏢 Official
Published by the company or team that built the technology.