release

Automates release preparation for GitHub repositories by auditing documentation, updating CHANGELOG, and committing changes.

5|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/jketreno/clare --skill release-jketreno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/jketreno/clare/tree/main/.codex/skills/release
Command: npx skills add https://github.com/jketreno/clare --skill release-jketreno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the preparation of release collateral by auditing documentation, updating the CHANGELOG, and managing code commits, simplifying the release process for repositories.

Core Features & Use Cases

  • Automated Auditing: Ensures all documentation is accurate and up-to-date before release.
  • CHANGELOG Management: Updates the CHANGELOG with user-facing summaries of new features and fixes.
  • Commit and Push Automation: Automates the staging, committing, and pushing of changes related to the release.

Quick Start

Prepare for a release by running the 'release' skill.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate CHANGELOG updates and commit checks for a GitHub repository release?

To automate CHANGELOG updates and commit checks for a GitHub repository release, use this Skill to audit documentation, generate user-facing summaries of new features, and stage code commits automatically. It ensures your repository is ready for publishing.

What is the best way to prepare release collateral for a repository workflow?

The best way to prepare release collateral for a repository workflow is to automate the auditing of documentation and the updating of CHANGELOG entries. This approach automatically verifies that all commits are ready and accurately documented before the final release.

Do I need a clean git tree to automate repository release preparation?

Yes, you need a clean git tree to automate repository release preparation. The automated checks require a clean working directory and your current branch set to 'main' to properly stage, commit, and push the release collateral without conflicts.

Can I use automated checks to ensure documentation is accurate before a code release?

Yes, you can use automated checks to ensure documentation is accurate before a code release. The Skill performs automated auditing across your repository to verify that all documentation matches the latest commits and updates the CHANGELOG accordingly.

Why does my release preparation workflow require a branch set to main?

Release preparation requires a branch set to 'main' to maintain repository workflow integrity. Automating commits and pushes from the main branch ensures that the updated CHANGELOG and audited documentation are integrated into the primary project history safely.