release

Automate pre-release validation of changelog, versioning, tests, and documentation.

142|19|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/joa23/linear-cli --skill release-joa23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/joa23/linear-cli/tree/main/.claude/skills/release
Command: npx skills add https://github.com/joa23/linear-cli --skill release-joa23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-release rigor is often skipped, leading to missed changelog entries, inconsistent version numbers, failing tests, and outdated documentation. This skill provides a structured checklist to ensure all release artifacts are accurate and ready.

Core Features & Use Cases

  • Determine the next release version by aligning commits and breaking changes with semantic versioning.
  • Update CHANGELOG.md, synchronize version numbers across files, run tests, and verify documentation before tagging.
  • Validate a clean working tree and perform a quick build and smoke test to confirm readiness.

Quick Start

Guide me through a release prep for the current project by following the pre-release checklist.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate pre-release validation for versioning and changelog updates?

Automate pre-release validation by verifying a clean working tree, updated changelog, consistent version numbers, and passing tests before tagging. This ensures changelog, versioning, tests, and documentation are in sync before releasing.

What is the best way to prepare a semantic versioning checklist for a feature release?

Determine the next release version by aligning commits and breaking changes with semantic versioning. Update CHANGELOG.md, synchronize version numbers across files, run tests, and verify documentation before tagging.

Why does my release pipeline fail when the changelog is out of sync with version numbers?

Release pipelines fail when changelog entries and version numbers are inconsistent because pre-release validation checks for accurate release artifacts. Verifying a clean working tree and synchronizing versions prevents missed entries.

Can I use a release readiness checklist for hotfixes and major version updates?

Yes, the release readiness checklist handles common scenarios like hotfixes, feature releases, and major versions. It performs a quick build and smoke test to confirm readiness across versioned artifacts and CI pipelines.

Do I need a clean working tree to run pre-release tests and documentation checks?

Yes, pre-release validation requires a clean working tree to perform a quick build and smoke test. Verifying updated documentation and passing tests before tagging ensures all release artifacts are accurate and ready.