release-skills

Automate release management with changelog generation and version bumps.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/opensourceways/geo-workflow --skill release-skills-opensourceways
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-skills
Source: https://github.com/opensourceways/geo-workflow/tree/main/.claude/skills/release-skills
Command: npx skills add https://github.com/opensourceways/geo-workflow --skill release-skills-opensourceways

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates release management by auto-detecting project configuration and version files, generates changelogs, and streamlines version bump workflows.

Core Features & Use Cases

  • Auto-detects project config and version files across Node.js, Python, Rust, Claude Plugin, and generic projects.
  • Changelog generation and update integrated with version bumps and release commits.
  • Guided release workflow including optional dry-run, verification prompts, and tagging.

Quick Start

Run /release-skills to auto-detect configuration and prepare a release.

Frequently Asked Questions about release-skills

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

FAQPage Schema
How do I automate changelog generation and version bumps for my Node.js or Python project?

Automate release management by running the release command to auto-detect project configuration, generate changelogs from conventional commits, update version files, and guide version bumps across Node.js, Python, Rust, and generic projects.

Can I use this release workflow tool to manage versioning across a monorepo with multiple languages?

Yes, this release workflow tool supports monorepos by auto-detecting project configuration and version files across Node.js, Python, Rust, and generic projects to streamline version bumps and changelog updates.

How does conventional-commit style mapping work when generating a changelog?

Conventional-commit style mapping parses your git commit history to automatically categorize changes, generating a structured changelog and determining the appropriate version bump for your release.

What is the best way to perform a dry-run before committing a version bump?

Use the guided release workflow's optional dry-run feature to preview changelog generation and version file updates, with verification prompts ensuring you confirm before applying the release commit and tagging.

Does the automated release process require manual confirmation before creating git tags?

No, the guided workflow includes optional confirmation prompts during the release process, allowing you to verify changelog updates and version bumps before finalizing the release commit and applying tags.