Release review

Skill Komluc/agent-skills-production/skills/release-review

Production-grade agent skills for Claude Code, OpenAI Codex, Gemini CLI, and every platform implementing the Agent Skills open standard

Install

npx -y skills add Komluc/agent-skills-production --skill release-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Prepares a complete release review by comparing the previous git tag with main. Use when work is complete and ready for a release candidate. Do not use for intermediate reviews during active development. Requires git in PATH.

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.1 KB, 377 tokens by cl100k_base, as published. Nobody here has run it

Step 1 — Fetch the diff

Run: scripts/fetch-diff.sh --output /tmp/release-diff.txt

Exit codes:

exit 0: diff generated — continue to Step 2
exit 1: no previous git tag found — ask the user to create a tag first (git tag v0.0.0 <sha>)
exit 2: git not available in PATH — stop and inform the user
exit 3: missing --output argument — skill configuration error

Step 2 — Analyze the diff

Read /tmp/release-diff.txt. Inspect for:

Breaking changes in public APIs (removed parameters, changed return types)
Behavioral regressions in existing functionality
Missing migration notes for breaking changes
Feature removals without prior deprecation notice
Dependency major version bumps without documented rationale

See references/release-criteria.md for complete criteria by change type.

Step 3 — Release decision

Start from "safe to release". Move to "blocked" only on concrete evidence found in the diff — not on suspicion or incomplete information.

Required output format — use exactly this structure:

Release readiness review
========================

Release call: 🟢 GREEN — safe to release

OR if blocked:

Release readiness review
========================

Release call: 🔴 BLOCKED

Unblock checklist:
- [ ] [Specific action — cite the exact file:line from the diff as evidence]
- [ ] [Another specific action with diff evidence]

Rules: