generate-version-changelog-markdown

Name: generate-version-changelog-markdown
Availability: InStock
Author: Lucca

Generates GitHub release changelog markdown from milestone pull requests.

52|7|Updated Apr 12, 2017

Search Tags:#changelog #markdown #breaking changes #release notes #pull requests #github release #milestone

Ready to run

npx skills add https://github.com/LuccaSA/lucca-front --skill generate-version-changelog-markdown-luccasa

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: generate-version-changelog-markdown
Source: https://github.com/LuccaSA/lucca-front/tree/main/.claude/skills/generate-version-changelog-markdown
Command: npx skills add https://github.com/LuccaSA/lucca-front --skill generate-version-changelog-markdown-luccasa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing a release changelog for lucca-front by hand means reviewing every PR in a milestone, classifying it, detecting breaking changes, and formatting entries consistently. This Skill automates that entire editorial workflow. ## Core Features & Use Cases - Milestone PR retrieval and filtering: Fetches PRs via the GitHub CLI and GraphQL API, excluding closed-unmerged PRs, branch-sync PRs, and `No log` labeled PRs. - Classification and formatting: Sorts PRs into sections (Features, Fixes, UI update, Documentation, Technical, Deprecated) with normalized PascalCase component prefixes derived from Angular selectors. - Breaking change detection: Scans the version diff for removed exports, inputs, CSS variables, and peer dependency changes beyond what labels indicate, then writes migration actions. - Use Case: When releasing lucca-front version 22.0, run this Skill to produce the complete GitHub Release body, including Actions required to update, Schematics, and a count of included PRs. ## Quick Start Generate the changelog markdown for lucca-front version 22.0 from its GitHub milestone.

Frequently Asked Questions about generate-version-changelog-markdown

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

FAQPage Schema

How do I generate a GitHub release changelog from milestone PRs?▼

Fetch the milestone number with the GitHub CLI, list its pull requests via the GraphQL API, filter out closed-unmerged and sync PRs, then classify each PR into sections and format entries as markdown list items with PR links.

How to detect breaking changes in a release without labels?▼

Compare the previous release tag against the release branch diff, checking for removed public API exports, deleted inputs or outputs, removed CSS variables and classes, peer dependency changes, and narrowed type unions. Confirm each signal is not a false positive like a re-export or rewritten line.

What sections does a minor version changelog include?▼

A minor version includes Actions required to update, Actions suggested, Schematics, Features, UI update, Fixes, Documentation, Technical, and Deprecated sections, in that order. Empty sections are never displayed.

Which pull requests are excluded from the changelog?▼

PRs closed without merging, PRs labeled No log, and branch synchronization PRs such as master-to-release merges and version bumps are excluded. Open PRs in the milestone are included since they are expected to ship.

How are component prefixes named in changelog entries?▼

Prefixes derive from the component's Angular selector, not its folder: strip the lu prefix and version suffix, then convert to PascalCase, so lu-core-select becomes [CoreSelect]. Cross-cutting changes use fixed prefixes like [Colors], [Icons], or [Tokens].