project-release_skill

This skill automates semantic versioning, changelog updates, and GitHub releases for ris-claude-code, ensuring consistent releases.

Shell

65

GitHub Stars

3

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill serejaris/ris-claude-code --skill project-release

README.md1.2 KB
README.ru.md1.8 KB
SKILL.md2.5 KB

Overview

This skill automates the release process for the ris-claude-code project. It standardizes semantic versioning, changelog updates, README checks, git tagging, pushes, and creation of GitHub releases. Use it to ensure consistent, repeatable public releases and to avoid common release mistakes.

How this skill works

The skill inspects the repository state, determines the appropriate version bump (major/minor/patch according to simple rules), and guides updates to CHANGELOG.md and READMEs when needed. It provides the exact git commands for committing, tagging, and pushing, then generates a GitHub release with structured notes and comparison links. Finally it offers post-release verification checks to confirm tags, release visibility, and working changelog links.

When to use it

When you are ready to publish a new version of ris-claude-code.
When adding a new skill or component to the repository.
When making updates to existing skills or performing bug fixes that require a release.
When a stakeholder asks you to cut a release or prepare release notes.

Best practices

Run the pre-release checklist: commit all changes, decide version bump, and confirm README updates only if skills list changed.
Follow semantic versioning rules: new skill = MINOR bump; updates/bugfixes/docs = PATCH bump.
Always update CHANGELOG.md with the release section and ensure comparison links at the bottom point to correct tags.
Only update READMEs (including the English README and the translated README) if the skills list changed to avoid unnecessary churn.
Create an annotated git tag and push both commits and tags before creating the GitHub release.
Use the provided GitHub CLI release template for consistent release notes and a link to the full changelog comparison.

Example use cases

Release v1.6.0 after adding a new skill component and updating the changelog.
Cut v1.5.2 to publish a bug-fix and include the fix under the "Fixed" section of CHANGELOG.md.
Prepare and push a release when asked by a maintainer, including creating the annotated tag and GitHub release with comparison links.
Run the post-release verification checklist to confirm tags, GitHub release presence, and working changelog links.

FAQ

Use semantic rules: add a MINOR bump for new skills/components and a PATCH bump for updates, bug fixes, or docs-only changes. Get the current tag with git describe --tags --abbrev=0.

When should I update READMEs?

Update README files only if the skills list changed (added or removed skills). Otherwise update only the changelog and release metadata.

What commands create the GitHub release?

Use the GitHub CLI template: gh release create vX.Y.Z --title "vX.Y.Z — Short Description" --notes "..." with notes that include a short summary and a link to the full changelog comparison.