afc:launch

Generate CHANGELOG entries, README updates, and GitHub release notes from git history.

7|Updated Feb 19, 2026

Search Tags:#changelog #versioning #documentation #publishing #release #github release

Ready to run

npx skills add https://github.com/jhlee0409/all-for-claudecode --skill afc-launch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: afc:launch
Source: https://github.com/jhlee0409/all-for-claudecode/tree/main/skills/launch
Command: npx skills add https://github.com/jhlee0409/all-for-claudecode --skill afc-launch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the generation of release artifacts, streamlining the process of preparing and publishing new software versions.

Core Features & Use Cases

Automated Changelog Generation: Creates new entries for CHANGELOG.md based on git history.
README Updates: Conditionally updates README.md with relevant release information.
Release Notes Draft: Generates a draft for GitHub release notes.
Use Case: After completing a set of features, use this Skill to automatically update your documentation and prepare release notes, ensuring consistency and saving significant manual effort.

Quick Start

Use the afc:launch skill to prepare release artifacts for version v1.0.0.

Frequently Asked Questions about afc:launch

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

FAQPage Schema

How do I automatically generate a changelog from git history for a new release?▼

You can automatically generate changelog entries by analyzing git history to create new CHANGELOG.md entries. This process extracts commit information to build release artifacts, ensuring documentation consistency without manual effort.

What is the best way to prepare GitHub release notes from recent commits?▼

The best way to prepare GitHub release notes is to use an automated utility that drafts them directly from git history. It identifies breaking changes and generates a draft, streamlining the release preparation process.

Can I automatically update README.md when publishing a new software version?▼

Yes, you can conditionally update README.md with relevant release information during the publishing process. This ensures your project documentation stays synchronized with the new version details automatically.

Does automated release preparation support detecting breaking changes?▼

Yes, automated release preparation supports breaking change identification. It analyzes your git history and optional spec context to detect breaking changes and includes them in the generated release notes and changelog entries.

How do I detect the correct version number for a software release from git history?▼

You can detect the correct version number using automated version detection features during release preparation. This mechanism analyzes your git history to determine the appropriate version bump for your new release artifacts.