final-release-review

Diff BASE_TAG...TARGET to produce a ship or block release decision.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/redacharf/fin-punk --skill final-release-review-redacharf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: final-release-review
Source: https://github.com/redacharf/fin-punk/tree/main/.agents/skills/final-release-review
Command: npx skills add https://github.com/redacharf/fin-punk --skill final-release-review-redacharf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to perform a deterministic, evidence-based release-readiness review by comparing the previous release tag with the latest candidate and auditing the BASE_TAG...TARGET diff for potential breaking changes, regressions, risks, and improvement opportunities.

Core Features & Use Cases

  • Automated tag synchronization and base/target selection to ground release decisions.
  • Diff analysis across key domains (code, configuration, tests) to surface risk signals and validation needs.
  • Guided gate policy and a structured release decision output (ship or block) with actionable next steps.

Quick Start

Sync remote tags, determine BASE_TAG and TARGET, then run the release-review workflow to produce a ship/block decision.

Frequently Asked Questions about final-release-review

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

FAQPage Schema
How do I perform a release readiness review by diffing previous and target tags?

Release readiness review identifies the previous release tag and latest target, then evaluates the BASE_TAG...TARGET diff to surface risks, regressions, and breaking changes for a deterministic ship/block decision.

What is deterministic release gating and how does it evaluate code diffs?

Deterministic release gating applies explicit gate rules and a review checklist to map code, configuration, and test diffs, ensuring evidence-based release decisions instead of manual guesswork.

How do I sync remote tags and select the base tag for a release audit?

Sync remote tags to determine the BASE_TAG and TARGET, grounding the release audit by mapping the full diff to validate readiness and identify potential blockers before shipping.

Can I get actionable unblock steps when a release gate finds issues?

When the release gate identifies issues, the workflow outputs actionable unblock steps alongside the structured ship or block decision, detailing exactly what to fix before re-evaluating.

Does release review work without external dependencies or integrations?

Release review operates with no external dependencies, using internal diff analysis and explicit gate rules to audit code, configuration, and test domains for release validation.