Claude Cursor Skill

changelog

AI DevKit · Update CHANGELOG.md Unreleased items from git commits since the latest release. Use when users ask to update changelog/release notes from recent commits, with one concise line per commit and commit/PR links.

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download codeaholicguy-ai-devkit-skills_changelog-ac73d58.zip · 1 KB

codeaholicguy/ai-devkit 1639 257 forks Apache-2.0 Updated 1d ago

Part of codeaholicguy/ai-devkit — 24 skills

Install

skills CLI npx skills add https://github.com/codeaholicguy/ai-devkit/tree/main/skills/changelog

Claude Code

claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install codeaholicguy-ai-devkit@llmmart

Git git clone https://github.com/codeaholicguy/ai-devkit.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole codeaholicguy/ai-devkit collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Changelog

Update the top Unreleased list in CHANGELOG.md from commits after the latest release.

Workflow

Find the latest release base:
- Prefer the latest reachable tag: git describe --tags --abbrev=0.
- If there are no tags, search recent history for a release commit and use that hash.
Get commits: git log <base>..HEAD --reverse --format='%H%x09%s'.
Derive the GitHub repo URL from git remote get-url origin.
For each commit, add one concise changelog line:
- Format: - [<short-hash>](<url>) <one-line summary>
- If the commit clearly relates to a PR, link the hash to the PR URL instead of the commit URL.
- Detect PRs from subjects like (#123), merge commits, or gh pr list --search <hash> --state all --json number,url.
Insert the new lines into the top Unreleased section/list in CHANGELOG.md.
- If no Unreleased section exists, create one at the top.
- Do not create a dated release heading unless the user asks for a release.

Rules

Keep one line per commit.
Preserve the existing changelog style when obvious.
Always add entries to the top Unreleased list.
Skip noisy commits only when clearly non-user-facing and explain what was skipped.
Do not invent PR links; use commit links when PR evidence is missing.

Files (ai-devkit)

agents

openai.yaml 301 B

interface:
  display_name: "Changelog"
  short_description: "AI DevKit · Update CHANGELOG.md Unreleased items from recent commits"
  default_prompt: "Use $changelog to update the top Unreleased list in CHANGELOG.md from git commits after the latest release, with one concise linked line per commit."

SKILL.md 1.5 KB

---
name: changelog
description: AI DevKit · Update CHANGELOG.md Unreleased items from git commits since the latest release. Use when users ask to update changelog/release notes from recent commits, with one concise line per commit and commit/PR links.
---

# Changelog

Update the top `Unreleased` list in `CHANGELOG.md` from commits after the latest release.

## Workflow

1. Find the latest release base:
   - Prefer the latest reachable tag: `git describe --tags --abbrev=0`.
   - If there are no tags, search recent history for a release commit and use that hash.
2. Get commits: `git log <base>..HEAD --reverse --format='%H%x09%s'`.
3. Derive the GitHub repo URL from `git remote get-url origin`.
4. For each commit, add one concise changelog line:
   - Format: `- [<short-hash>](<url>) <one-line summary>`
   - If the commit clearly relates to a PR, link the hash to the PR URL instead of the commit URL.
   - Detect PRs from subjects like `(#123)`, merge commits, or `gh pr list --search <hash> --state all --json number,url`.
5. Insert the new lines into the top `Unreleased` section/list in `CHANGELOG.md`.
   - If no `Unreleased` section exists, create one at the top.
   - Do not create a dated release heading unless the user asks for a release.

## Rules

- Keep one line per commit.
- Preserve the existing changelog style when obvious.
- Always add entries to the top `Unreleased` list.
- Skip noisy commits only when clearly non-user-facing and explain what was skipped.
- Do not invent PR links; use commit links when PR evidence is missing.