ln-63-release-publisher

Prepares and publishes tagged GitHub releases from repository evidence after user approval.

556|83|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-63-release-publisher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-63-release-publisher
Source: https://github.com/levnikolaevich/claude-code-skills/tree/main/plugins/maintainer-suite/skills/ln-63-release-publisher
Command: npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-63-release-publisher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Publishing a release involves version selection, release notes, validation gates, tagging, and GitHub Release creation, and mistakes in any step can leave a broken or misleading public release. This Skill enforces an evidence-based checklist so every release is reproducible, verified, and published only after explicit approval.

Core Features & Use Cases

  • Evidence-Based Release Preparation: Inspects commits, tags, manifests, and repository policy to determine the correct version, tag shape, and release scope instead of guessing conventions.
  • Structured Release Notes: Groups changes by user outcome, documents breaking changes with migration steps, and verifies install commands against current documentation.
  • Gated Publication Workflow: Runs repository release gates, presents the exact tag, notes, and validation evidence, and waits for explicit user approval before tagging or publishing.
  • Use Case: A maintainer asks to release version 2.1 of a plugin. The Skill reviews commits since the last tag, drafts notes in the repository's house style, runs validation from a clean checkout, presents the full proposal, and only after approval creates the annotated tag and GitHub Release.

Quick Start

Ask the assistant to prepare and publish a new GitHub release for this repository using the release publisher workflow.

Frequently Asked Questions about ln-63-release-publisher

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

FAQPage Schema
How do I create a GitHub release with proper release notes?

Inspect commits since the previous tag, group changes by user outcome, and verify install commands against current documentation. This Skill drafts the notes, runs validation gates, and publishes only after you approve the exact tag and notes.

How to choose the right version number for a release?

Follow the repository's declared versioning policy rather than imposing SemVer or CalVer. The Skill reads repository release rules and prior tags, and stops to ask when the release target or tag is ambiguous.

Can I publish a release without manual approval steps?

No. The Skill always presents the exact version changes, tag, notes, and validation evidence, then waits for explicit approval before committing, tagging, or publishing. Edits after approval trigger a new approval round.

What happens if a GitHub release fails partway through?

If failure occurs before the tag is public, the Skill stops and preserves evidence. If a public tag exists but release creation fails, it reports the exact partial state and never deletes or moves a published tag without approval.

Does this publish packages to npm or PyPI automatically?

No. The Skill only creates the Git tag and GitHub Release. Publishing to npm, PyPI, NuGet, or container registries requires separate explicit authorization, and no community announcement is created as a side effect.