skills.rest
christophevg
christophevgCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

release

Bump C3 plugin versions, update changelogs, and push annotated git tags.

Updated Mar 26, 2026
Search Tags:#changelog#versioning#GitHub#release#semantic versioning#marketplace#git tagging
One-click install
npx skills add https://github.com/christophevg/c3 --skill release-christophevg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/christophevg/c3/tree/main/.claude/skills/release
Command: npx skills add https://github.com/christophevg/c3 --skill release-christophevg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents release confusion by guiding you through version bumping, changelog updates, tagging, and publishing for the C3 plugin in a repeatable way.

Core Features & Use Cases

  • Version bump decisioning: Chooses major, minor, or patch semantics aligned to breaking changes, new features, or bug fixes.
  • Release artifact updates: Updates the plugin version and moves changelog content from an Unreleased section into a dated release entry.
  • GitHub publication workflow: Creates an annotated git tag and pushes tags so the marketplace and GitHub release process can pick up the new version.

Quick Start

Use the release skill to prepare a new patch release by bumping the version, updating the changelog, creating the tag, and pushing tags to GitHub.

Frequently Asked Questions about release

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

FAQPage Schema
How do I manage semantic versioning and prepare a GitHub release for a plugin?▼

Semantic versioning for a GitHub release requires selecting a major, minor, or patch bump, updating plugin.json, moving changelog entries from Unreleased to a dated section, creating an annotated git tag, and pushing tags to the main branch.

When should I use a major, minor, or patch version bump for a new release?▼

Choose a major, minor, or patch version bump based on your changes: major for breaking changes, minor for new features, and patch for bug fixes, ensuring semantic versioning consistency across your release artifacts.

How do I update a changelog from an Unreleased section into a dated release entry?▼

Updating a changelog for a release involves moving content from the Unreleased section into a newly dated release entry that matches the updated semantic version in your plugin configuration file.

What is the process for creating an annotated git tag and pushing it for marketplace availability?▼

Creating an annotated git tag and pushing tags to the main GitHub branch triggers downstream marketplace availability, allowing the new plugin version to be picked up by the release process.

Do I need to update plugin.json and CHANGELOG.md consistently for every version bump?▼

Yes, a consistent release requires updating both plugin.json and CHANGELOG.md simultaneously when applying any semantic version bump to prevent release confusion and ensure downstream marketplace processes function correctly.

Related Skills

Explore More Product & Management Skills→
gmcabritagmcabrita
6

update-changelog

Aggregate unreleased Git commits into the CHANGELOG.md Unreleased section.

Community
Intermediate
OliverOuyangOliverOuyang
1

release

Automate version bumps, tests, git tags, npm publish, and GitHub releases for oh-my-claudecode.

Community
Advanced
AgLyx3AgLyx3

Changelog Generator

Parse Conventional Commits into Keep a Changelog release notes.

Community
Advanced
yangtaihong59yangtaihong59
97

siyuan-plugin-pub

Synchronize SiYuan plugin version files, changelog, and bilingual README timelines.

Community
Intermediate