release

Automate git releases with changelog generation and semantic versioning.

4|Updated Dec 5, 2025
One-click install
npx skills add https://github.com/aaaa47080/stock_agent --skill release-aaaa47080
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/aaaa47080/stock_agent/tree/main/.opencode/skills/release
Command: npx skills add https://github.com/aaaa47080/stock_agent --skill release-aaaa47080

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the release process by generating semantic-versioned tags and changelogs, reducing manual drift during software releases.

Core Features & Use Cases

  • Semantic version bumping according to release notes
  • Changelog generation from conventional commits or commit messages
  • GitHub release publishing with notes and assets if provided

Quick Start

Trigger a new release by specifying the version and changelog notes, then execute the release workflow to create a Git tag and GitHub release.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate git releases with changelog generation and semantic versioning?

Automating git releases involves generating a changelog from conventional commits, bumping the semantic version, tagging, and publishing a GitHub release. This skill enforces semantic versioning and automated changelog creation to reduce manual drift during software releases.

What is the best way to generate a changelog from commit messages for a new release?

Generating a changelog from commit messages is handled automatically during the release workflow. The skill extracts conventional commits or standard commit messages to create release notes, ensuring the changelog accurately reflects repository history.

Does this release automation tool support publishing GitHub releases with assets?

Publishing GitHub releases with notes and assets is supported. When you trigger a new release by specifying the version and changelog notes, the workflow creates a Git tag and publishes the GitHub release with any provided assets.

Can I use semantic version bumping without manually writing release notes?

Semantic version bumping can be performed without manual notes by relying on automated changelog creation. The skill derives the version bump and generates the changelog directly from your repository's conventional commits or commit messages.

What do I need to trigger a new git release workflow?

To trigger a new git release, you need to specify the target version and the changelog notes. Executing the release workflow then automatically creates the associated Git tag and publishes the corresponding GitHub release.