release-check

Audit release artifacts and documentation for version alignment and completeness.

Updated Feb 2, 2026

Search Tags:#changelog #versioning #documentation #release #artifacts #quality-check #api-docs

Ready to run

npx skills add https://github.com/drillan/marketschema --skill release-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-check
Source: https://github.com/drillan/marketschema/tree/main/.claude/skills/release-check
Command: npx skills add https://github.com/drillan/marketschema --skill release-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill validates release readiness by auditing artifacts and documentation for a software release.

Core Features & Use Cases

Artifact Checks: Verifies spec.md, plan.md, and tasks.md exist and that tasks are fully completed.
Documentation Checks: Ensures README.md and CHANGELOG.md have required sections.
Versioning & API: Confirms version alignment across package.json and CHANGELOG, and that API docs exist when contracts are present.
Use Case: Before publishing a release, it outputs a ReleaseChecklist detailing readiness, gaps, and recommended fixes.

Quick Start

Run: npx skills run release-check Or via an AI agent: User: Check if we're ready for release

Frequently Asked Questions about release-check

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

FAQPage Schema

How do I check if my software release artifacts and documentation are ready?▼

You can check release readiness by running a validation audit that verifies spec.md, plan.md, and tasks.md exist and are complete. The check also ensures README.md and CHANGELOG.md contain required sections for proper release documentation.

How do I verify version alignment between package.json and CHANGELOG before publishing?▼

Verifying version alignment involves confirming the version specified in package.json matches the corresponding release entry in CHANGELOG.md. This consistency check prevents publishing releases with mismatched version numbers across project artifacts.

Do I need API documentation if my project has contracts defined?▼

API documentation is required if your project includes defined contracts. The release validation process checks for this alignment, ensuring API docs exist whenever contracts are present before you approve a release.

What files are required for a spec kit release validation check?▼

Required files for a spec kit release validation include spec.md, plan.md, and tasks.md for artifacts, alongside README.md and CHANGELOG.md for documentation. The check confirms these files exist and that all documented tasks are fully completed.

Can I use a script to automate release readiness checks for my project?▼

You can automate release readiness checks by running validation scripts that audit artifacts and documentation. The script outputs a ReleaseChecklist detailing readiness, identifying gaps, and providing recommended fixes before publishing.