Changelog
Claude Code plugin with skills for daily dev workflows — commits, standups, PRs, design docs, and GitHub automation.
npx -y skills add ForeverAProgrammer/claude-devflow --skill changelogAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Generate or update a changelog file that accumulates history across all releases.
SKILL.md
1.9 KB, as published. Nobody here has run it
Generate or update a changelog file that accumulates history across all releases.
Rules:
- Tagged release sections are permanent — never modify them.
- Only the
## Unreleasedsection at the top is updated on each run. - If
CHANGELOG.mddoes not exist, create it from scratch using all tags.
Steps:
- Run
git tag --sort=-version:refnameto list all tags. - Check if
CHANGELOG.mdexists.
If CHANGELOG.md does not exist, generate the full changelog from scratch. For each tag (newest first), run git log <previous-tag>..<tag> --oneline to get commits for that release (for the oldest tag, use the first commit as the base). Group and format commits under a ## <tag> heading. After all tagged sections, add an ## Unreleased section for commits since the most recent tag; omit it if there are none. Write the full result to CHANGELOG.md.
If CHANGELOG.md exists, only update the ## Unreleased section. Run git tag --sort=-version:refname | head -1 to find the most recent tag, then git log <last-tag>..HEAD --oneline to get commits since it. Replace the existing ## Unreleased section with a freshly generated one, or prepend a new one if absent. Leave all other sections untouched.
Formatting rules for each section:
- Group commits by type: Features (
feat), Bug Fixes (fix), Performance (perf), Documentation (docs), Chores & Maintenance (chore,refactor,style,test,ci). Omit empty groups. - Write each entry as a plain-English bullet point — not the raw commit message. Include the short commit hash at the end in parentheses.
- For the
## Unreleasedheading, append the suggested next semver bump in parentheses if the last tag is semver: bump patch for fixes only, minor for any feat, major for anyBREAKING CHANGE.
$ARGUMENTS