pre-release-validation

Validate project release readiness with structured JSON results.

Updated Dec 29, 2025
One-click install
npx skills add https://github.com/jayteealao/Aperture --skill pre-release-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-release-validation
Source: https://github.com/jayteealao/Aperture/tree/main/.claude/skills/pre-release-validation
Command: npx skills add https://github.com/jayteealao/Aperture --skill pre-release-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill validates release readiness for a project by performing comprehensive pre-release checks.

Core Features & Use Cases

  • Validate version integrity against configured version files and tags.
  • Check changelog entries, git state, and required files before release.
  • Run project-type specific validations and optional custom checks across languages and ecosystems.

Quick Start

Run the pre-release-validation tool with your new version, changelog path, and list of modified files. Example: pre-release-validation --new-version 1.2.0 --changelog CHANGELOG.md --modified-files fileA.txt,fileB.js

Frequently Asked Questions about pre-release-validation

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

FAQPage Schema
How do I validate release readiness for a new project version?

To validate release readiness, run a pre-release validation tool with your new version, changelog path, and modified files to perform comprehensive checks across version integrity, git state, and project configurations.

What checks are needed before a CI release?

Pre-release CI validation requires checking version integrity against configured tags, verifying changelog correctness, ensuring a clean git state, and running project-type specific validations across multiple languages.

Can I skip specific validation checks during the release process?

Yes, pre-release validation supports configurable skip lists, allowing you to bypass specific project-type validations or custom checks while still receiving blocking errors, warnings, and recommendations in a structured JSON format.

How do I verify changelog correctness and git state before tagging a release?

Verifying changelog correctness and git state requires a pre-release validation tool that cross-references your new version against configured version files and tags, returning structured blocking errors if the git state is invalid.

Does pre-release validation work across different programming languages and ecosystems?

Yes, pre-release validation runs project-type specific validations and optional custom checks across multiple languages and ecosystems, ensuring broad release readiness regardless of your development environment.

What is the best way to automate version integrity checks before publishing?

Automating version integrity checks involves running a pre-release validation command with parameters like --new-version, --changelog, and --modified-files to systematically verify release readiness and output structured recommendations.