changelogs

Name: changelogs
Availability: InStock
Author: Tiendanube

Generate and update CHANGELOG.md entries from branch commits.

29|5|Updated Jul 8, 2022

Search Tags:#automation #git #changelog #packages #release-notes #change-log #pr-prep

Ready to run

npx skills add https://github.com/TiendaNube/nimbus-design-system --skill changelogs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelogs
Source: https://github.com/TiendaNube/nimbus-design-system/tree/main/.cursor/skills/changelogs
Command: npx skills add https://github.com/TiendaNube/nimbus-design-system --skill changelogs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the generation and updating of CHANGELOG.md entries based on changes detected in the current branch.

Core Features & Use Cases

Identify changed files across the branch and map them to affected packages to update corresponding CHANGELOG.md entries.
Prepend concise release notes to the relevant changelog files for release preparation.
Use Case: When preparing a PR, run this skill to automatically update package and root changelogs with a summary of changes.

Quick Start

Run the changelogs skill on a branch with changes to automatically generate and apply changelog entries. The skill analyzes commits, detects affected packages, and updates the appropriate CHANGELOG.md files according to project conventions.

Frequently Asked Questions about changelogs

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

FAQPage Schema

How do I automatically generate changelog entries from git commits?▼

You can automatically generate changelog entries by analyzing git commits on your current branch to detect affected packages and prepend concise release notes to the corresponding CHANGELOG.md files.

What is the best way to update CHANGELOG.md files for PR preparation?▼

The best way to update CHANGELOG.md files for PR preparation is to analyze branch changes, map affected files to their respective packages, and automatically apply formatted changelog entries based on repository conventions.

Can I update multiple package changelogs from a single branch?▼

Yes, you can update multiple package changelogs from a single branch by detecting changed files, mapping them to affected packages, and updating both the specific package CHANGELOG.md files and the root changelog as needed.

How do release notes generation tools map commits to affected packages?▼

Release notes generation tools map commits to affected packages by analyzing the file changes within the current branch history and updating the appropriate package or root CHANGELOG.md files according to project conventions.

Does automated changelog generation work without predefined repository conventions?▼

Automated changelog generation relies on the repository's existing changelog conventions to compose properly formatted entries, so it requires predefined project conventions to accurately structure the release notes.

Why are my automated changelog entries not reflecting recent branch changes?▼

Automated changelog entries might not reflect recent branch changes if the git history analysis fails to detect affected files or if the repository's changelog conventions are not properly configured to format the updates.