final-release-review

Audit a release candidate diff against the previous git tag for breaking changes and regressions.

Updated May 23, 2026
One-click install
npx skills add https://github.com/kiranimmadi2/promptforge-ai --skill final-release-review-kiranimmadi2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: final-release-review
Source: https://github.com/kiranimmadi2/promptforge-ai/tree/main/openai-agents-python/.agents/skills/final-release-review
Command: npx skills add https://github.com/kiranimmadi2/promptforge-ai --skill final-release-review-kiranimmadi2

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Before shipping a new version of openai-agents-python, maintainers need a consistent, evidence-based review of everything that changed since the last release tag. This Skill automates that audit: it locates the previous release tag from remote git tags, maps the full diff to the target commit, and produces a decisive ship-or-block release gate call with concrete evidence instead of guesswork. ## Core Features & Use Cases - Automated tag discovery: A bundled shell script fetches remote tags and returns the newest tag matching a configurable pattern (default v*). - Structured diff analysis: Guided commands (git diff --stat, --dirstat, --name-status, --word-diff) map hot directories, deleted tests, and risky files between the base tag and target commit. - Deterministic release gate: Explicit blocking triggers (confirmed regressions, unversioned breaking API changes, data-loss or security risks, broken build paths) prevent inconsistent ship/block calls, and every finding requires Evidence, Impact, and Action. - Use Case: Before tagging v0.4.2 of openai-agents-python, run the skill to diff v0.4.1 against origin/main, surface a renamed public function without a migration note, and receive a BLOCKED call with an unblock checklist. ## Quick Start Ask the AI to use the final-release-review skill to audit the diff between the latest release tag and origin/main and produce a ship or block release readiness report.

Frequently Asked Questions about final-release-review

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

FAQPage Schema
How do I review a git diff before releasing a new version?

Fetch remote tags, identify the previous release tag, then run git diff --stat, --dirstat, and --name-status between the base tag and target commit. Inspect suspicious files with git diff --word-diff and classify each finding by severity with evidence, impact, and action.

How do I find the latest release tag in a git repository?

Run git fetch origin --tags --prune, then git tag -l 'v*' --sort=-v:refname | head -n1 to get the newest version-sorted tag. The included find_latest_release_tag.sh script automates this and accepts a custom remote and tag pattern.

What counts as a breaking change in a release diff?

Breaking changes include removed or renamed public modules, classes, or functions, changed parameter or return types, altered config defaults, protocol or schema shape changes, and dependency major bumps. They only block a release when versioning or migration notes are missing or mismatched.

When should a release be blocked versus shipped?

Block only with concrete evidence: a confirmed regression, an unversioned breaking API change, an unresolved data-loss or security issue, or a broken build path. Large diffs, broad refactors, or unrun local tests alone are not blocking triggers.

Can I use a custom tag pattern instead of v* for releases?

Yes. Pass a custom pattern as the second argument to find_latest_release_tag.sh, such as '*.*.*', and optionally a different remote as the first argument. The script fetches tags from that remote before selecting the newest match.