final-release-review

Diff BASE_TAG...TARGET to assess release readiness and gate decisions.

3.6k|897|Updated May 31, 2025
One-click install
npx skills add https://github.com/openai/openai-agents-js --skill final-release-review-openai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: final-release-review
Source: https://github.com/openai/openai-agents-js/tree/main/.agents/skills/final-release-review
Command: npx skills add https://github.com/openai/openai-agents-js --skill final-release-review-openai

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps teams validate release readiness by systematically diffing the previous release tag against the current candidate commit to surface breaking changes, regressions, risks, and required follow-ups.

Core Features & Use Cases

  • Deterministic diff assessment between BASE_TAG...TARGET to identify potential release blockers.
  • Structured risk logging with actionable next steps and unblock criteria.
  • Gate-driven workflow that combines tag synchronization, base/target selection, and evidence-based decisions.

Quick Start

Run the quick-start steps to fetch the latest remote tag, determine the base tag, and generate a deterministic diff and risk assessment.

Frequently Asked Questions about final-release-review

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

FAQPage Schema
How do I validate release readiness using a git diff between tags?

Release readiness validation involves diffing the BASE_TAG...TARGET commit range to identify breaking changes, regressions, and risks. A deterministic gate policy then evaluates this diff alongside a review checklist to decide whether to ship or block the release candidate.

What is a deterministic release gate and how does it work?

A deterministic release gate evaluates a BASE_TAG...TARGET diff against a review checklist and structured risk logging criteria. It enforces consistent ship or block decisions by requiring evidence-based validation rather than manual judgment during release workflows.

How do I assess breaking changes and risks before cutting a release tag?

Assess breaking changes and risks by generating a deterministic diff between your previous release tag and current candidate commit. The review checklist and structured risk logging capture actionable next steps and unblock criteria for identified release blockers.

Does this release review workflow require git as a dependency?

Yes, git is a required dependency for this release review workflow. It uses git to fetch the latest remote tag, determine the base tag, and generate the deterministic diff between base and target commits for evidence-based release gating.

What is the best way to automate release validation for the OpenAI Agents SDK?

Automating release validation for the OpenAI Agents SDK is best handled by diffing the BASE_TAG...TARGET range to detect breaking changes and regressions. Applying a gate-driven workflow with structured risk logging ensures deterministic ship or block decisions.

When should I block a release candidate based on a tag diff?

You should block a release candidate when the BASE_TAG...TARGET diff reveals breaking changes, regressions, or unresolved risks failing the deterministic gate policy. Structured risk logging provides actionable next steps and unblock criteria to address these release blockers.