release

Coordinate timepicker-ui releases with versioning, changelog, and docs synchronization.

95|20|Updated Oct 27, 2020
One-click install
npx skills add https://github.com/pglejzer/timepicker-ui --skill release-pglejzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/pglejzer/timepicker-ui/tree/main/.claude/skills/release
Command: npx skills add https://github.com/pglejzer/timepicker-ui --skill release-pglejzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and coordinates a complete timepicker-ui release workflow, ensuring version consistency, changelog synchronization, and documentation updates across the repository. It does not perform git commits, tagging, or npm publishing, but guides the user through those steps.

Core Features & Use Cases

  • Orchestrates the end-to-end release flow (audit → approve → apply) using the build-release subagent to generate a coherent plan.
  • Enforces the root package.json as the single source of truth for the library version, while keeping docs-app references and changelogs in sync.
  • Guides cross-repo updates: README, CHANGELOG.md, and docs-site content to reflect the new version without modifying unrelated apps.

Quick Start

Start a release by letting the skill propose a version bump and guide you through the audit, apply, and sanity build steps.

Frequently Asked Questions about release

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

Library release automation coordinates version bumping and changelog updates by using the root package.json as the single source of truth. It generates a structured plan to synchronize documentation references before applying changes.

What is the best way to keep documentation in sync during a version release?

Documentation synchronization during a release ensures README, CHANGELOG.md, and docs-site content reflect the new version. The workflow uses the root package.json version to update cross-repo references without modifying unrelated applications.

How does a gated release workflow prevent publishing errors?

A gated release workflow prevents errors by enforcing an audit, approve, and apply sequence. This structured flow validates the version bump and changelog updates before any changes are applied, ensuring consistency without auto-committing.

Can I run a sanity build before publishing without triggering a git commit?

Yes, you can run a sanity build without triggering a git commit. The release workflow executes the build to verify changes after applying the version bump, but it explicitly avoids performing git commits, tagging, or npm publishing.

Does this release workflow handle npm publishing automatically?

No, this release workflow does not handle npm publishing automatically. It guides the user through the preparation steps and sanity build, but the actual git commits, tagging, and npm publishing must be performed manually.

When do I need an end-to-end release coordination process for my timepicker-ui library?

You need end-to-end release coordination when updating the timepicker-ui library to ensure version consistency. It orchestrates the entire flow, from proposing a version bump to executing documentation updates and performing a final build verification.