Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
drillan avatar

Release Check

  • 53 installs
  • 3 repo stars
  • Updated January 21, 2026
  • drillan/speckit-gates

Runs a pre-release validation pass so a solo builder confirms planning, implementation and docs are all ready before shipping a release.

About

release-check is a Claude Code skill from the speckit-gates package, which adds automated quality gates to the spec-kit workflow. It runs a manual pre-release validation pass and reports a GREEN/YELLOW/RED status, so a solo builder can confirm that planning, implementation and docs are all in order before cutting a release.

  • Pre-release validation gate
  • Confirms release readiness
  • GREEN/YELLOW/RED status output

Release Check by the numbers

  • 53 all-time installs (skills.sh)
  • Ranked #138 of 248 Release Management skills by installs in the Skillselion catalog
  • Data as of Jul 29, 2026 (Skillselion catalog sync)
npx skills add https://github.com/drillan/speckit-gates --skill release-check

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs53
repo stars3
Last updatedJanuary 21, 2026
Repositorydrillan/speckit-gates

What it does

Runs a pre-release validation pass so a solo builder confirms planning, implementation and docs are all ready before shipping a release.

Who is it for?

Developers using spec-kit doing a final check before release

When should I use this skill?

Right before cutting a release, to confirm readiness

Files

SKILL.mdMarkdownGitHub ↗

release-check

Validates release readiness before creating a release.

Purpose

This skill validates that all artifacts are complete and consistent for release:

  • Spec kit artifacts: spec.md, plan.md, tasks.md exist and are complete
  • Documentation: README.md, CHANGELOG.md have required sections
  • Versioning: Version numbers are consistent across package.json and CHANGELOG
  • API docs: API documentation matches contract specifications

Output

The skill outputs a ReleaseChecklist with:

  • Overall readiness status (Ready/Not Ready)
  • Individual check items with pass/fail/skip status
  • Version consistency information
  • Specific issues to address before release

Usage

This is a manual skill - run it before creating a release:

npx skills run release-check

Or via AI agent:

User: Check if we're ready for release

Exit Codes

CodeStatusMeaning
0ReadyAll checks pass
1Not ReadySome checks failed
3ErrorRequired files missing

Checks Performed

Artifact Checks (FR-022)

CheckRequirement
spec.md existsRequired
plan.md existsRequired
tasks.md existsRequired
All tasks completeRequired

Documentation Checks (FR-023)

CheckRequirement
README.md existsRequired
README.md has usage sectionRequired
CHANGELOG.md existsRequired
CHANGELOG.md has unreleased sectionRequired

Version Checks (FR-026)

CheckRequirement
package.json version presentOptional
CHANGELOG.md version presentOptional
Versions matchIf both present

API Checks (FR-025)

CheckRequirement
contracts/ existsOptional
API docs exist if contractsRequired if contracts
Endpoints documentedRequired if contracts

Checklist Output Format

## Release Checklist

**Status**: Ready to Release / Not Ready

### Artifacts
| Status | Check | Details |
|--------|-------|---------|
| [PASS] | spec.md exists | |
| [PASS] | plan.md exists | |
| [FAIL] | All tasks complete | 5 tasks remaining |

### Documentation
| Status | Check | Details |
|--------|-------|---------|
| [PASS] | README.md exists | |
| [SKIP] | API docs | No contracts/ directory |

Recommendations

If release check fails:

1. Complete all remaining tasks in tasks.md 2. Ensure README.md has a usage section 3. Update CHANGELOG.md with release notes 4. Verify version numbers are consistent 5. Run release-check again to verify fixes

Related skills

Release Managementtestingdevops

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.