release

Automate Prismstack releases with tests, changelogs, version bumps, and git tags.

2|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/fagemx/prismstack --skill release-fagemx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/fagemx/prismstack/tree/main/.claude/skills/release
Command: npx skills add https://github.com/fagemx/prismstack --skill release-fagemx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release a new Prismstack version by running tests, updating changelogs, bumping version numbers, tagging, and reinstalling globally.

Core Features & Use Cases

  • Automates the end-to-end release workflow, ensuring pre-flight checks and reproducible builds.
  • Manages version bumps and changelog updates in alignment with semantic versioning.
  • Tags releases and reinstalls globally to validate the production-ready artifact. Use Case: A maintainer releases a new Prismstack version after code is merged, ensuring a clean, test-backed deployment.

Quick Start

Run the release command and follow the prompts to finalize a Prismstack release.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate software versioning and changelog generation for multi-module repositories?

Automating software versioning calculates semantic version bumps, inserts changelog entries, and tags git releases across multi-module repositories. It ensures pre-flight checks pass before deployment to maintain reproducible builds.

How does a release workflow prevent deployment when there are uncommitted changes?

A release workflow prevents deployment by enforcing guardrails that detect active changes before tagging. It satisfies pre-release checks to ensure the repository is clean and tests pass before finalizing the version.

Can I run tests and verify global installation during an automated deployment?

You can run tests and verify global installation during deployment by executing test suites before tagging, then reinstalling the artifact globally to validate the production-ready build.

What is the best way to manage semantic versioning and git tagging for a new release?

The best way to manage semantic versioning and git tagging is to automate version calculation, apply the version bump, and generate the git tag automatically after tests and changelog updates succeed.

Does automated release management work with existing changelog formats?

Automated release management works with changelogs by inserting generated entries during the release process. It aligns updates with semantic versioning rules while managing version bumps across the repository modules.