release

Execute release steps from RELEASE.md and verify brew install for prove_it.

199|8|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/searlsco/prove_it --skill release-searlsco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/searlsco/prove_it/tree/main/.claude/skills/release
Command: npx skills add https://github.com/searlsco/prove_it --skill release-searlsco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the release process for the prove_it tool, ensuring that new versions are properly documented and published.

Core Features & Use Cases

  • Automated Release Process: Execute the release steps in the project's RELEASE.md file.
  • Version Control: Ensures that the version number is updated and reported.
  • Brew Install Verification: Confirms that the brew install command for prove_it succeeds.
  • Use Case: When prompted to cut a release, publish a new version, or "ship" prove_it, this Skill handles the necessary steps.

Quick Start

Run the release skill to initiate the version release process for prove_it.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate the release process for a tool using a predefined steps file?

To automate the release process, this Skill executes the predefined steps in a project's RELEASE.md file. It handles version control updates and verifies the brew install command to ensure the new version is properly published.

What is the best way to cut a release and ship a new version of a tool?

The best way to cut a release and ship a new version is to run this Skill, which automates the entire workflow. It updates version numbers, executes documented release steps, and verifies the installation command succeeds.

Does release automation handle brew install verification for version control?

Yes, release automation handles brew install verification by confirming the command succeeds after updating the version number. This ensures the published version control update is fully functional and accessible to users.

Can I use this release automation Skill for any project management workflow?

You can use this release automation Skill for project management workflows specifically needing to streamline the release process of the prove_it tool. It executes predefined steps from project documentation to ensure proper version control.

Why does my release process fail when I manually update the version control?

Your release process might fail due to missed steps in the project documentation or an unverified brew install command. This Skill prevents such failures by automating the predefined release steps and confirming installation success.

What are the limitations of using a predefined release automation process for my build?

A limitation of this predefined release automation process is its specific suitability for the prove_it tool. It strictly follows the project's RELEASE.md steps, meaning it may not adapt to custom build process requirements outside this scope.