release

Coordinate Synapse version releases by updating metadata, changelog, and GitHub release.

29|3|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/Vincentwei1021/Synapse --skill release-vincentwei1021
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/Vincentwei1021/Synapse/tree/main/.claude/skills/release
Command: npx skills add https://github.com/Vincentwei1021/Synapse --skill release-vincentwei1021

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you reliably publish a new Synapse version by coordinating the exact release steps—reviewing changes, updating the changelog and version, creating a GitHub tag, and verifying the release—so you don’t miss required updates or publish incorrect notes.

Core Features & Use Cases

  • Changelog-ready diff review: identifies commits after the last version tag and summarizes only release-worthy changes.
  • Structured CHANGELOG updates: adds a new top section with consistent Added/Changed/Fixed/Plugin grouping and formatting rules.
  • Version bump + GitHub release automation: updates package.json per semver, then creates the GitHub release with notes containing only the new changelog section.
  • Release verification checklist: confirms the tag exists locally and the GitHub release is visible.

Quick Start

Ask your AI assistant to follow the Synapse release process to bump the version, update CHANGELOG.md with the correct grouped sections, and create a GitHub release for main with notes containing only the new changelog content.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate GitHub release creation with a correctly formatted changelog?

To automate GitHub release creation, you review commits since the previous version tag, append a new grouped section to CHANGELOG.md, bump the version in package.json, and execute gh release create using only that new section as notes.

How does semver version bumping work when publishing a new release tag?

Semver version bumping requires updating package.json metadata based on reviewed changes, ensuring the new tag correctly increments major, minor, or patch numbers before creating the GitHub release.

What is the best way to generate changelog sections from git commit history?

Generating changelog sections from git history involves using git to detect the previous version tag, diffing the commit range, and summarizing release-worthy changes into structured Added, Changed, Fixed, or Plugin groups.

Do I need gh installed to create a GitHub release for my project?

Yes, you need gh installed because the release process uses the gh release create command to publish the new tag and attach the extracted changelog notes to the GitHub repository.

Why does my GitHub release show incorrect notes when updating CHANGELOG.md?

GitHub release notes appear incorrect when the extracted text includes unrelated history, so you must limit the notes passed to gh release create strictly to the newly added changelog section.

Can I use this release automation workflow for projects other than Synapse?

This release automation workflow is specifically designed for the Synapse release process, coordinating exact steps like version metadata updates and grouped changelog formatting tailored to that project.