Release Skill

Automate version bumping and release preparation for the Simple Language compiler.

Updated May 27, 2026
One-click install
npx skills add https://github.com/ormastes/Spipe --skill release-skill-ormastes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Release Skill
Source: https://github.com/ormastes/Spipe/tree/main/doc/00_llm_process/skill_command/skills/pipe/release
Command: npx skills add https://github.com/ormastes/Spipe --skill release-skill-ormastes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual, error-prone work of version bumping across multiple files, updating the changelog, and performing the standard release steps for the Simple Language compiler.

Core Features & Use Cases

  • Deterministic version bumping: Supports patch/minor/major increments and accepts an explicit X.Y.Z version to keep releases consistent across teams.
  • Multi-file version synchronization: Updates simple.sdn, VERSION, and hardcoded fallback version strings in two CLI sources so the runtime and tooling agree.
  • Release hygiene automation: Creates a structured changelog entry, generates a signed commit and annotated tag, and enforces an explicit confirmation step before pushing.

Quick Start

Ask the AI to run the release with the exact command you want, for example: “Perform a patch release for the Simple Language compiler using /release.”

Frequently Asked Questions about Release Skill

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

FAQPage Schema
How do I automate version bumping and changelog updates for a compiler release?

To automate version bumping and changelog updates, the Skill updates version sources like simple.sdn and VERSION, inserts a top-of-file changelog entry, creates a signed commit, and generates an annotated git tag.

What is the best way to synchronize CLI fallback version strings across multiple project files?

The best way to synchronize CLI fallback version strings is to rewrite hardcoded values in CLI source files to match the runtime version read from simple.sdn, ensuring tooling and runtime agree.

Does this release automation tool support explicit X.Y.Z versioning and semantic version increments?

Yes, the release automation tool supports explicit X.Y.Z versioning alongside patch, minor, and major increments by validating the release argument format before applying the update to the project.

How do I safely push git tags and release commits without unapproved network operations?

To safely push git tags, the Skill generates guarded push instructions that enforce an explicit confirmation step before executing any network operations, preventing unapproved pushes while creating local commits and tags.

Can I set a specific custom version number instead of using automatic semantic version bumps?

Yes, you can set a specific custom version number by providing an explicit X.Y.Z argument, which the system validates and applies across all project sources instead of calculating an automatic increment.

Why do I need to validate the release argument format before updating project version sources?

Validating the release argument format before updating sources ensures only legitimate semantic versions or explicit X.Y.Z strings are processed, preventing corruption of the VERSION file and CLI fallback strings.