post-release

Validate GitHub Release artifacts, notes, changelog, and deployment steps.

31|5|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/NSEvteev/FullSpec --skill post-release-nsevteev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post-release
Source: https://github.com/NSEvteev/FullSpec/tree/main/.claude/skills/post-release
Command: npx skills add https://github.com/NSEvteev/FullSpec --skill post-release-nsevteev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-release validation automates the verification of post-release publishing artifacts to ensure that Release, Release Notes, and Deployment steps are correctly completed after creating a GitHub Release.

Core Features & Use Cases

  • Release consistency checks: verifies that the Release, notes, and changelog reflect the published version.
  • Deployment validation: confirms deployment steps completed or are properly skipped per configuration.
  • Audit trail: provides a reference checklist aligned with the SSOT workflow for post-release checks.

Quick Start

Run /post-release --version <vX.Y.Z> to validate the release publication.

Frequently Asked Questions about post-release

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

FAQPage Schema
How do I validate GitHub Release notes and changelog consistency after publishing?

To validate GitHub Release publication, run a post-release check to ensure Release notes, changelog, and deployment steps reflect the published version. This verifies release consistency and confirms deployment steps completed or were properly skipped per configuration.

What is post-release validation in a CI/CD pipeline?

Post-release validation is an automated verification process for post-release publishing artifacts. It ensures that GitHub Releases, release notes, and deployment steps are correctly completed after creating a release, providing an audit trail aligned with the SSOT workflow.

How do I check if a deployment step was correctly skipped during a GitHub Release?

You can validate deployment steps post-release by applying an optional skip flag for the deploy check. This confirms whether deployment steps were properly skipped or completed according to your CI/CD pipeline configuration.

How do I enforce a specific version format when validating release artifacts?

To enforce a version format during post-release validation, provide the target version using the required version input flag. This ensures the Release, notes, and changelog accurately reflect the specific published version format.

Can I output post-release validation results as JSON?

Yes, you can output post-release validation results as JSON. This optional feature allows you to programmatically consume the verification status of Release notes, changelog, and deployment steps across your CI/CD pipelines.

What should I check if my GitHub Release publication is missing changelog updates?

If your changelog is missing updates, run a post-release validation to verify release consistency. This checks that the Release, notes, and changelog accurately reflect the published version and identifies missing publishing artifacts.