release-changelog

Generates stable Paperclip changelogs from Git commit history, GitHub pull requests, and Calab for versioning/release tracking.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/tamzi/theorg --skill release-changelog-tamzi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-changelog
Source: https://github.com/tamzi/theorg/tree/main/.agents/skills/release-changelog
Command: npx skills add https://github.com/tamzi/theorg --skill release-changelog-tamzi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python, git, github-api, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of release changelogs for Paperclip, saving time and reducing manual errors in documenting changes.

Core Features & Use Cases

  • Automated Changelog Generation: Automatically generates user-facing changelogs for stable Paperclip releases.
  • Versioning Model: Utilizes calendar versioning for stable releases.
  • Integration with Git and GitHub: Integrates with Git for commit history and GitHub for pull request information.
  • Breaking Changes Detection: Identifies and flags breaking changes with upgrade paths.
  • User-Friendly Sections: Organizes changes into sections like 'Breaking Changes', 'Highlights', and 'Fixes'.

Quick Start

Generate the changelog for the next stable release by running the command: ./scripts/release-changelog.sh YYYY.MDD.P.

Frequently Asked Questions about release-changelog

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

FAQPage Schema
How do I generate a release changelog from git commit history and pull requests?

To generate a release changelog, this Skill analyzes git commit history, changesets, and merged GitHub pull requests to produce structured documentation. It automatically organizes entries into sections like 'Breaking Changes', 'Highlights', and 'Fixes' for stable releases.

What is the best way to automate changelog generation for calendar versioning releases?

Automating changelog generation for calendar versioning involves running a script with the target version format, such as `./scripts/release-changelog.sh YYYY.MDD.P`. This automatically extracts and categorizes merged pull requests and git changes into user-facing release notes.

Do I need Python and GitHub API access to automate release documentation?

Yes, you need Python and specific libraries along with GitHub API access to automate release documentation. These dependencies are required to pull commit history and merged pull request data for analyzing changesets and detecting breaking changes.

Can automated changelog tools detect breaking changes and provide upgrade paths?

Automated changelog tools can detect breaking changes by analyzing commit history and pull request data. This Skill specifically identifies breaking changes, flags them in a dedicated section, and includes upgrade paths to guide users through stable release transitions.

How does calendar versioning work for software release tracking?

Calendar versioning for software release tracking uses a date-based format like YYYY.MDD.P to label stable releases. This Skill integrates with Git and GitHub to map merged changesets and pull requests to these chronological version numbers for accurate release tracking.