agentsclimarketplace

Changelog

Skill vvelikodny/velikodnys-claude-code/skills/changelog

Generate a curated changelog from the most important commits in the current PRFrom its SKILL.md

Install
npx -y skills add vvelikodny/velikodnys-claude-code --skill changelog

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 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.

SKILL.md

2.7 KB, as published. Nobody here has run it

GENERATE PR CHANGELOG

You generate a curated changelog entry from the current PR's commits. NOT a git log dump — a compiled summary of notable user-facing changes.

STEPS

  1. Get the current PR's base branch and metadata:
gh pr view --json number,title,body,baseRefName -q '"\(.number) \(.title) [base: \(.baseRefName)]"'
  1. Get all commits in this PR (current branch vs base):
BASE=$(gh pr view --json baseRefName -q '.baseRefName') && git log --oneline --no-merges "$(git merge-base HEAD "origin/$BASE")..HEAD"
  1. Get the combined diff stat for context on what actually changed:
BASE=$(gh pr view --json baseRefName -q '.baseRefName') && git diff --stat "$(git merge-base HEAD "origin/$BASE")..HEAD"
  1. If needed, read specific changed files to understand the nature of changes better.

FILTERING RULES

Skip these commits — they are NOT changelog-worthy:

  • chore: commits (deps, CI, gitignore, symlinks, formatting)
  • docs: commits that only fix typos or formatting
  • merge commits
  • commits that only change lockfiles, .gitignore, or CI configs
  • refactors with no user-visible behavior change

KEEP these commits — they ARE changelog-worthy:

  • feat: — new features
  • fix: — bug fixes
  • commits with ! in header or BREAKING CHANGE footer — always include
  • security: — vulnerability fixes
  • docs: that add new documentation for new features
  • any commit that changes public API, config format, or user-visible behavior

OUTPUT FORMAT

Follow the format defined in rules/docs/changelog.md. Use today's date. Group by change type.

YYYY-MM-DD
----------

### Added

- Description from user's perspective (#PR)

### Fixed

- Description from user's perspective (#PR)

Rules:

  • One line per change, start with -
  • Describe from user's perspective, NOT implementation details
  • Merge related commits into a single entry (e.g., 3 commits about OAuth → one "Added OAuth 2.0 support" line)
  • Reference the PR number at the end: (#123)
  • Only include categories that have entries (Added, Changed, Deprecated, Removed, Fixed, Security)
  • If ALL commits are chore/non-notable, say so explicitly — don't fabricate entries

AFTER GENERATING

Ask the user (numbered list):

  1. Insert into CHANGELOG.md and push — find existing CHANGELOG.md, add entry under the header before older dates, commit and push
  2. Just show the output — do nothing else

Keep looking

Skills are one crate of 608,475. 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.