repo-prepare-release

Analyze changelogs and package metadata to determine semantic version bumps across monorepo packages.

1.1k|32|Updated Apr 5, 2025
One-click install
npx skills add https://github.com/open-circle/formisch --skill repo-prepare-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-prepare-release
Source: https://github.com/open-circle/formisch/tree/main/skills/repo-prepare-release
Command: npx skills add https://github.com/open-circle/formisch --skill repo-prepare-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the release preparation process by analyzing changelogs, determining semantic version bumps, and updating package.json and CHANGELOG.md files across a monorepo.

Core Features & Use Cases

  • Changelog analysis: scan core and framework changelogs to identify unreleased changes.
  • Version bump determination: compute major/minor/patch bumps based on changes.
  • Apply updates: modify package.json versions and update corresponding CHANGELOG.md headers.
  • Use Case: For a multi-package repository, run this Skill to ensure consistent, documented releases across all packages.

Quick Start

Run the release preparation workflow to scan unreleased changes and apply updates to package.json and changelog files.

Frequently Asked Questions about repo-prepare-release

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

FAQPage Schema
How do I automate semantic version bumps across multiple packages in a monorepo?

Automating semantic version bumps across a monorepo involves analyzing changelogs to identify unreleased changes, computing the correct version increments, and applying those bumps to package.json files. This Skill reads known changelog locations to apply these updates safely.

How does changelog analysis determine semantic versioning for releases?

Changelog analysis for semantic versioning scans unreleased changes in your changelogs to calculate major, minor, or patch version bumps. It applies these determined semantic versions to package.json files and updates corresponding CHANGELOG.md headers.

Can I update CHANGELOG.md headers and package.json versions at the same time?

Yes, you can update CHANGELOG.md headers and package.json versions simultaneously during release preparation. The workflow modifies package metadata and updates corresponding changelog headers across core, methods, and framework packages in an idempotent manner.

What is the best way to prepare a consistent multi-package release?

The best way to prepare a consistent multi-package release is to run an automated workflow that scans unreleased changes across all packages, computes version bumps, and applies uniform updates to both package.json and CHANGELOG.md files.

Is this release automation safe to run multiple times in a monorepo?

Yes, this release automation is safe to run multiple times because it applies changes in an idempotent manner. Repeated executions will not duplicate version bumps or corrupt changelog headers, ensuring safe releases across your monorepo setup.