post-release

Name: post-release
Availability: InStock
Author: oogdz

Validate GitHub Release notes, CHANGELOG updates, and deployment statuses after publication.

Updated Apr 2, 2026

Search Tags:#automation #changelog #github #validation #release #notes #deploy

Ready to run

npx skills add https://github.com/oogDZ/2 --skill post-release

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-release validation streamlines the process of verifying Release notes, CHANGELOG updates, and deployment status to ensure a correct and verified public publication after a GitHub Release.

Core Features & Use Cases

Validate Release notes presence and accuracy against the release description.
Verify CHANGELOG has been updated and matches the released version.
Confirm deployment status across environments and flag any failures for remediation.
Use Case: After creating a GitHub Release, run the skill to ensure the publication is complete and visible as expected.

Quick Start

Execute /post-release --version <vX.Y.Z> to validate the latest GitHub 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 a GitHub release after publishing?▼

To validate a GitHub release, you can run a post-release check to verify release notes, confirm CHANGELOG updates, and check deployment status across environments. This ensures the publication is complete and accurate.

What does post-release validation check for in a GitHub deployment?▼

Post-release validation checks for the presence and correctness of release artifacts, verifies the CHANGELOG matches the released version, and confirms the deployment status across environments to flag any failures.

How do I ensure my release notes match the GitHub release description?▼

You can ensure release notes match the description by running a validation check that verifies their presence and accuracy against the actual GitHub release description after the release is created.

Can I verify CHANGELOG updates automatically after a GitHub release?▼

Yes, you can verify CHANGELOG updates automatically by running a validation process that checks whether the CHANGELOG has been updated and correctly matches the released version.

What is the best way to confirm deployment status across environments after a release?▼

The best way to confirm deployment status is to run a validation skill that checks deployments across all environments after a GitHub release is created, flagging any failures for remediation.