release-review

Surface static analysis, version consistency, changelog, and git hygiene issues before release.

18|4|Updated Jan 29, 2026

Search Tags:#changelog #versioning #build #release #static-analysis #pre-release #tests

Ready to run

npx skills add https://github.com/chrisallenlane/claude-swe-workflows --skill release-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-review
Source: https://github.com/chrisallenlane/claude-swe-workflows/tree/main/skills/release-review
Command: npx skills add https://github.com/chrisallenlane/claude-swe-workflows --skill release-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-release readiness is a complex coordination problem. This Skill surfaces critical checks (static analysis, version consistency, changelog coverage, and git hygiene) and presents findings for human decision-making before shipping.

Core Features & Use Cases

Static analysis pass to identify blockers
Version consistency checks across manifests and source
Changelog coverage and license compliance validation
Interactive decision points for proceeding with tests, builds, and doc review
Use Case: before tagging a new release, run a comprehensive preflight to surface issues and decide a release path

Quick Start

Run the /release-review command on the release branch to trigger static analysis and a human-reviewed readiness report.

Frequently Asked Questions about release-review

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

FAQPage Schema

How do I check pre-release readiness for version consistency and changelog gaps before tagging?▼

Pre-release readiness checks validate version consistency across manifests, identify changelog coverage gaps, and surface static analysis blockers before you tag a release. Running a preflight review presents these findings for human decision-making before shipping.

What is included in a preflight release validation workflow?▼

A preflight release validation workflow includes static analysis passes, version consistency checks across modules, changelog coverage validation, license compliance checks, and git hygiene problem detection to ensure comprehensive release readiness.

How do I enforce checks for debug artifacts and breaking changes before shipping a build?▼

Enforce checks for debug artifacts and breaking changes by running a preflight release review that surfaces static analysis results and interactive decision points for tests, builds, and documentation freshness before shipping.

Can I apply pre-release validation across multiple modules and repositories?▼

Yes, pre-release validation can be applied across multiple modules and repositories to enforce checks for version consistency, license compliance, manifests, and documentation freshness as part of a human-in-the-loop review.

What's the best way to coordinate static analysis and documentation freshness before a release?▼

Coordinate static analysis and documentation freshness by running a comprehensive preflight release review that surfaces blockers, version consistency issues, and changelog gaps, presenting findings through interactive decision points for proceeding with tests and builds.

Why does my release branch fail version consistency checks before tagging?▼

Release branches fail version consistency checks when static analysis detects mismatched versions across manifests and source files, or when changelog coverage and license compliance validation reveal gaps requiring human review before proceeding.