agentsclimarketplace

Changelog writer

Skill kakarot-oncloud/claude-dev-skills/skills/changelog-writer

15 practical Claude Agent Skills for software developers — commit messages, PR descriptions, code review, SQL, regex, tests, migrations, and more. Official SKILL.md format, ready to upload to Claude.ai.

Install
npx -y skills add kakarot-oncloud/claude-dev-skills --skill changelog-writer

Assembled 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

Writes CHANGELOG.md entries in Keep a Changelog format from a list of commits, PRs, or a diff between two versions. Groups changes into Added, Changed, Deprecated, Removed, Fixed, Security. Use this skill when the user asks to "update the changelog", "write release notes", needs entries for a new version bump, or wants to convert git log output into a readable changelog.

SKILL.md

2.6 KB, as published. Nobody here has run it

Changelog Writer

You produce CHANGELOG.md entries following Keep a Changelog 1.1.0 and SemVer.

Format

## [1.4.0] - 2026-04-19

### Added
- New `--dry-run` flag for the migrate command (#142)

### Changed
- Default timeout increased from 5s to 30s for slow networks

### Deprecated
- `parseConfig()` — use `loadConfig()` instead, will be removed in 2.0

### Removed
- Legacy v0 API endpoints (`/api/v0/*`)

### Fixed
- Race condition when refreshing tokens during concurrent requests (#138)

### Security
- Bumped `lodash` to 4.17.21 to patch CVE-2021-23337

Categories (use only those that apply)

  • Added — new features
  • Changed — changes to existing functionality
  • Deprecated — features still working but to be removed
  • Removed — features removed in this version
  • Fixed — bug fixes
  • Security — vulnerability fixes (always include CVE if known)

Rules

  1. Audience is the user/integrator, not the contributor. "Added a flag" not "Implemented argparse handler in cli.py".
  2. One entry per user-visible change. Squash multiple commits that fixed one bug into one entry.
  3. Skip internal changes — refactors, test additions, CI tweaks — unless they affect users (e.g. perf improvement).
  4. Reference issues/PRs with (#123) at the end of the entry, not as a link in the middle.
  5. Breaking changes: prefix with **BREAKING:** and explain migration in the description.
  6. Date format: YYYY-MM-DD.
  7. Version order: newest at the top.
  8. Unreleased section at the very top for in-flight changes: 
    ## [Unreleased]
### Added
- ...

Process

  1. Get the input (commit list, PR titles, or diff).
  2. Filter out non-user-facing changes.
  3. Group by category.
  4. Rewrite each in past tense, present-user-impact phrasing.
  5. Recommend the version bump (major / minor / patch) based on what's in the changelog:
    • Has Removed or Breaking → major
    • Has Added → minor
    • Only Fixed/Security → patch

Output the markdown ready to paste at the top of CHANGELOG.md, plus a one-line version bump recommendation.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.