mcpField
R
release-check

release-check

github.com/drillanTesting & quality353 installsUpdated 40w ago
Repository

About release-check

A manual skill for checking whether a project is ready for release. It produces a checklist covering required artifacts, documentation, version consistency, and API docs, with issues and readiness status.

Key features

  1. 01Spec artifact completeness checks
  2. 02README and changelog checks
  3. 03Package and changelog version checks
  4. 04API documentation checks
  5. 05Readiness status and issue details

Use cases

  1. 01Checking readiness before a release
  2. 02Finding missing required project artifacts
  3. 03Verifying version and API documentation consistency

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/drillan/speckit-gates --skill release-check

After installing, type/release-checkin Claude Code to confirm it loaded.

Bundled filesscripts/check.sh

Details

From the project README

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

Comments

Markdown supported