release

Generate and update CHANGELOG, README, and docs from git history.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated documentation updates — CHANGELOG, README, and docs — fully automatic, with no confirmations.

Core Features & Use Cases

  • Automatically generate and append changelog entries from commit messages
  • Sync README and docs with the latest release notes
  • Supports standard Keep a Changelog formatting and version sections

Quick Start

Run the release workflow to automatically generate and update CHANGELOG, README, and docs after each merge.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate changelog generation from git commit messages?

Automated changelog generation parses git commit history to append entries automatically. It extracts commit messages, formats them into Keep a Changelog sections, and updates documentation without manual input.

What is the Keep a Changelog format and when do I need it for release documentation?

Keep a Changelog is a standardized format for maintaining release documentation with organized version sections. You need it when managing software releases to ensure consistent records of changes across versions.

Can I sync README and docs with the latest release notes automatically?

Yes, you can sync README and docs with release notes automatically. The workflow updates markdown documentation by pulling the latest release notes generated from git history, ensuring docs stay current.

Does this changelog automation work without manual confirmations?

Yes, this changelog automation runs fully automatically without manual confirmations. It executes the release workflow to generate and update CHANGELOG, README, and docs directly after each merge.

What is the best way to maintain consistent documentation across software releases?

The best way to maintain consistent documentation across releases is automating updates through git history analysis. This approach applies Keep a Changelog formatting and syncs version sections into README and docs automatically.

Do I need any dependencies to automate markdown documentation updates from git history?

No dependencies are required to automate markdown documentation updates from git history. The workflow operates independently to parse commits and apply Keep a Changelog formatting without external packages.