release-create

Bump versions, update changelogs, and publish GitHub releases.

19|3|Updated Jul 19, 2024
One-click install
npx skills add https://github.com/danielterra/FOUNDATION --skill release-create-danielterra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-create
Source: https://github.com/danielterra/FOUNDATION/tree/main/.claude/skills/release-create
Command: npx skills add https://github.com/danielterra/FOUNDATION --skill release-create-danielterra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the Foundation release process by bumping versions, updating changelogs and release metadata, and publishing a GitHub release, reducing manual steps and errors.

Core Features & Use Cases

  • Release automation: bump version, update CHANGELOG, SoftwareRelease.ttl, README, commits, and tags; publish a GitHub release.
  • Deterministic release steps: ensures consistency across repository artifacts and release notes.
  • Use Case: When preparing a new Foundation release, generate a version tag and publish the corresponding GitHub release.

Quick Start

Create a new Foundation release by bumping the version, updating changelog, and publishing a GitHub release.

Frequently Asked Questions about release-create

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 GitHub release?

You can automate a GitHub release by coordinating version bumps in Cargo.toml and package.json, updating CHANGELOG.md, and publishing the release artifacts to GitHub, ensuring deterministic steps and traceable changes.

What is the best way to synchronize release notes and version numbers across multiple repository files?

Synchronizing release metadata involves automatically updating version numbers and changelog entries across Cargo.toml, package.json, and CHANGELOG.md, then committing and tagging the changes before publishing a GitHub release.

Can I use this release automation for standard Cargo.toml and package.json workflows?

Yes, this release automation is designed for standard workflows across Cargo.toml, package.json, CHANGELOG.md, and release notes, ensuring consistency and auditability across all repository artifacts.

Does automated release management support rollback readiness and auditability?

Automated release management enforces deterministic steps for version bumping, artifact updates, commit tagging, and release publication, maintaining auditability and rollback readiness for your software releases.

How do I create a new Foundation software release with updated metadata and tags?

To create a Foundation release, the process bumps the version, updates the changelog and SoftwareRelease.ttl metadata, commits and tags the changes, and publishes the corresponding GitHub release.

What are the limitations of automating software release publication across repository artifacts?

The automation focuses on standard Foundation release workflows across Cargo.toml, package.json, and CHANGELOG.md, so non-standard artifact formats or custom release pipelines may require additional manual configuration or steps.