final-release-review

Analyzes commit history to identify untracked performance and/or quality defects.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/sisyphus1212/codex-fusion-starter-template --skill final-release-review-sisyphus1212
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: final-release-review
Source: https://github.com/sisyphus1212/codex-fusion-starter-template/tree/main/scaffold/.agents/skills/final-release-review
Command: npx skills add https://github.com/sisyphus1212/codex-fusion-starter-template --skill final-release-review-sisyphus1212

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Locating the previous release tag from remote tags and auditing the BASE_TAG...TARGET diff helps engineering teams assess release readiness and surface breaking changes, regressions, improvement opportunities, and risks before shipping.

Core Features & Use Cases

  • Deterministic gate policy that clearly marks GREEN LIGHT TO SHIP or BLOCKED with concrete unblock steps.
  • Tag discovery and diff analysis by fetching remote tags, selecting a base tag, and summarizing changes across the release boundary.
  • Actionable reporting that cites evidence, impact, and recommended actions aligned with governance and upgrade notes.

Quick Start

Run the quick-start to fetch the latest remote release tag and begin auditing the BASE_TAG...TARGET diff.

Frequently Asked Questions about final-release-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a git diff between release tags to check for breaking changes?

A deterministic release gate applies a fixed policy to classify diff results as GREEN LIGHT TO SHIP or BLOCKED, providing concrete unblock steps to ensure governance and release readiness.

Can I automate release-readiness reviews in my CI pipeline?

Release-readiness reviews require git to fetch remote tags, identify the previous base tag, and calculate the diff against the target commit to analyze breaking changes and regressions.

What is a deterministic gate policy for release management?

Release audit reports document findings with evidence, impact, and recommended actions, aligning the diff results with governance requirements and generating actionable upgrade notes.

How do I generate release notes from a git tag diff?

When a release gate is BLOCKED, the audit provides concrete unblock steps citing specific evidence and impact from the release diff, guiding developers to resolve regressions before shipping.