// Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
| name | changelog-generator |
| description | Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation. |
This skill transforms technical git commits into polished, user-friendly changelogs that your customers and users will actually understand and appreciate.
From your project repository:
Create a changelog from commits since last release
Generate changelog for all commits from the past week
Create release notes for version 2.5.0
Create a changelog for all commits between March 1 and March 15
Create a changelog for commits since v2.4.0, using my changelog
guidelines from CHANGELOG.md
User: "Create a changelog for commits from the past 7 days"
Checks if DEPENDENCIES.md is out of date by comparing it against gradle/libs.versions.toml and each module's build.gradle. Reports any version mismatches, missing dependencies, or removed dependencies.
This is a code review skill for Braintree Android SDK. Provide code review on the patch. Use when a PR is raised or the user asks for a code review.
Reproduces a merchant developer's reported issue with the Braintree Android SDK by scaffolding a minimal Demo app scenario that isolates the problem. Use when a merchant describes a bug, unexpected behavior, or integration question.