spotiarr-release

Coordinate version detection, CHANGELOG updates, package.json bumps, annotated tagging, and GitHub Release publishing.

41|6|Updated Nov 27, 2025
One-click install
npx skills add https://github.com/mralexsaavedra/spotiarr --skill spotiarr-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spotiarr-release
Source: https://github.com/mralexsaavedra/spotiarr/tree/main/skills/spotiarr-release
Command: npx skills add https://github.com/mralexsaavedra/spotiarr --skill spotiarr-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

This Skill prevents broken or inconsistent GitHub releases by standardizing the release workflow, including version bumps, changelog updates, tagging, and the final GitHub Release notes.

Core Features & Use Cases

  • Deterministic release preparation: Verifies the current root package version, updates CHANGELOG.md, and bumps only the root package.json (never workspace placeholders).
  • Safe Git tagging and publishing: Creates annotated tags with a required message and updates an existing GitHub Release body without changing the release name.
  • Release-body consistency: Uses the repository’s release-body template for clear, user-focused release notes tailored to the version being published.

Quick Start

Run the spotiarr-release process to bump the root version, update CHANGELOG.md, create an annotated tag, and update the GitHub Release notes from the provided template.

Frequently Asked Questions about spotiarr-release

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

FAQPage Schema
How do I automate GitHub release versioning and changelog updates?

Automating GitHub release versioning involves coordinating version detection, CHANGELOG.md updates, root package.json bumps, and annotated git tagging to ensure consistent semantic versioning and standardized release note publishing.

What is the best way to create annotated git tags for semantic versioning?

Creating annotated git tags for semantic versioning requires using the command git tag -a vX.Y.Z -m "vX.Y.Z". This approach attaches a required message to the tag, ensuring safe and traceable release tagging.

How do I update GitHub Release notes from a repository template?

Updating GitHub Release notes from a repository template involves using the gh release edit vX.Y.Z --notes command. This modifies the existing release body without changing the release name, ensuring release-body consistency.

Does this release automation workflow support npm workspace package.json files?

This release automation workflow does not support npm workspace package.json files. It strictly requires editing only the root package.json for version bumping, deliberately avoiding workspace placeholders to prevent broken or inconsistent releases.

How do I validate a GitHub release after publishing?

Validating a GitHub release after publishing requires using the gh release view command alongside workflow run listing. This verifies the release notes, annotated tags, and package version bumps were applied correctly.