comet-release

Prepares and validates Comet releases with user-facing changelogs and bilingual documentation.

2.9k|284|Updated May 14, 2026
One-click install
npx skills add https://github.com/rpamis/comet --skill comet-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comet-release
Source: https://github.com/rpamis/comet/tree/main/assets/skills-maintainer/comet-release
Command: npx skills add https://github.com/rpamis/comet --skill comet-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Preparing a software release involves many error-prone manual steps: determining the correct version scope, writing user-facing changelog entries, keeping bilingual website documentation in sync, and verifying that builds and generated assets are ready. This Skill automates that release preparation workflow for the Comet project while keeping Git delivery actions under explicit user authorization.

Core Features & Use Cases

  • Release Scope Determination: Reads package.json, lockfile metadata, changelog headers, branches, and previous release tags to compute the real release range and avoid duplicate versions.
  • User-Facing Changelog Writing: Categorizes changes into Added, Changed, Fixed, Removed, or Security using professional, neutral English focused on user-visible behavior.
  • Bilingual Docs Synchronization: Coordinates with the comet-bilingual-docs skill to keep the main repository and the website docs repository structurally consistent in Chinese and English.
  • Release Readiness Verification: Runs risk-appropriate checks such as affected tests, format checks, builds, generated asset validation, package dry-runs, and full test suites.
  • Use Case: Before tagging a new Comet beta or hotfix, invoke this Skill to produce the changelog entries, sync the website docs, and confirm all verification steps pass before authorizing commit and push.

Quick Start

Use the comet-release skill to prepare and verify the next Comet release based on the current branch and version range.

Frequently Asked Questions about comet-release

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

FAQPage Schema
How do I prepare a release changelog from git history?

Determine the release range from the previous tag, current branch, and origin/master, then list only user-visible changes. Categorize entries as Added, Changed, Fixed, Removed, or Security, describing behavior and value rather than implementation details.

How do I keep bilingual documentation in sync during a release?

Update both the main repository docs and the separate website docs repository so Chinese and English versions share the same structure and confirmed user-visible semantics. This Skill delegates that synchronization to the comet-bilingual-docs skill.

What checks should run before publishing an npm package release?

For documentation-only changes, run affected tests and format checks. For runtime, install, routing, or release metadata changes, also run the build, generated asset verification, package dry-run, and the full test suite.

Does this Skill commit, tag, or publish to npm automatically?

No. It only prepares release assets and verification results. Commits, pushes, tags, GitHub Releases, and npm publishing require separate explicit user authorization, with delivery handled through the comet-safe-delivery skill.

What happens if the current branch already has a higher version than master?

The Skill appends to or rewrites that existing version entry instead of creating a duplicate version in the changelog, keeping release history consistent.