skills.rest
AgenticFlowX
AgenticFlowXOFFICIAL
Explore all skills by this author →
GitHub

afx-release

Automate AFX release workflows with version bumping, changelog updates, tags, and GitHub releases.

19|1|Updated Apr 4, 2026
Search Tags:#version control#release automation#GitHub release#version bumping#changelog management
One-click install
npx skills add https://github.com/AgenticFlowX/agenticflowx --skill afx-release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: afx-release
Source: https://github.com/AgenticFlowX/agenticflowx/tree/main/apps/vscode/resources/skills/agenticflowx/afx-release
Command: npx skills add https://github.com/AgenticFlowX/agenticflowx --skill afx-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the release workflow for AFX, handling version bumping, updating the changelog, tagging, and publishing a GitHub release.

Core Features & Use Cases

  • Version Bumping: Automatically determines the next version based on commit history or explicit arguments.
  • Changelog Update: Generates a changelog entry based on commits since the last release.
  • Tagging and Publishing: Creates a tag and a GitHub release with the updated changelog.
  • Use Case: When you want to release a new version of AFX, this Skill can be used to automate the entire process, ensuring consistency and efficiency.

Quick Start

Run the command '/afx-release' to automatically detect and perform a release.

Frequently Asked Questions about afx-release

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

FAQPage Schema
How do I automate GitHub release workflow with version bumping and changelog generation?▼

Automating GitHub release workflow involves analyzing commit history to determine the next version, updating the changelog, creating a tag, and publishing the release via the GitHub API. This process ensures consistency and efficiency for new releases.

Do I need git and gh CLI installed to automate version bumping and tagging?▼

Yes, you need both git and gh CLI tools installed to automate version bumping and tagging. The automation process relies on git for commit history analysis and gh CLI for authenticating and interacting with the GitHub API to publish releases.

Can I automatically generate a changelog from commit history before a GitHub release?▼

Yes, you can automatically generate a changelog entry from commit history. The system analyzes commits made since the last release to compile the changelog, which is then attached to the newly published GitHub release.

What is the best way to determine the next version number for a release?▼

Determining the next version number can be automated by analyzing commit history or by providing explicit arguments. The system evaluates commit messages to decide the appropriate version bump for your release workflow.

When should I avoid automating the release workflow for version control?▼

You should avoid automating the release workflow if your project lacks structured commit history for changelog generation or if the required git and gh CLI dependencies are not configured in your current environment.

Related Skills

Explore More Software Engineering Skills→
JuanMS20JuanMS20

github-auth

Configure GitHub authentication for Hermes Agent using git, gh CLI, or SSH credentials.

Community
Intermediate
huyhung9630huyhung9630
1

omc-release

Guide software release preparation, versioning, and execution with confirmation.

Community
Advanced
Rune-kitRune-kit
82

git

Generate semantic commit messages and Pull Request descriptions from Git history.

Official
Advanced
ehtbantonehtbanton

semantic-release-config

Generate a semantic-release configuration file for automated versioning and publishing.

Community
Intermediate