Generate and update CHANGELOG.md entries from branch commits.
npx skills add https://github.com/TiendaNube/nimbus-design-system --skill changelogs
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
This Skill automates the generation and updating of CHANGELOG.md entries based on changes detected in the current branch.
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.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
montenokiGenerate git commit messages matching repository history style and conventions.
BasedHardwareParse conventional commits and update CHANGELOG.md with categorized markdown entries.
Rune-kitGenerate semantic commit messages and Pull Request descriptions from Git history.
jhlee0409Generate CHANGELOG entries, README updates, and GitHub release notes from git history.
