AgentStack
SKILL verified Apache-2.0 Self-run

Doncheli Changelog

skill-doncheli-don-cheli-sdd-doncheli-changelog · by doncheli

Auto-generate CHANGELOG.md entries from git commit history. Activate when user mentions "changelog", "release notes", "what changed", "generate changelog", "CHANGELOG", "release history".

No reviews yet
0 installs
11 views
0.0% view→install

Install

$ agentstack add skill-doncheli-don-cheli-sdd-doncheli-changelog

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Doncheli Changelog? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Don Cheli: Changelog Auto-Generator

Instructions

  1. Determine the commit range:
  • Default: from the last semver tag to HEAD
  • With --from/--to: use the specified refs
  • With --version: use that as the new version number
  1. Run git log --oneline and parse conventional commit prefixes
  2. Map commit types to Keep a Changelog categories:
  • feat / feat! → Added (breaking changes go in a separate top section)
  • fix → Fixed
  • refactor / perf → Changed
  • docs → Changed
  • security → Security
  • deprecated → Deprecated
  • remove → Removed
  • test / chore / ci → omit by default (include with --verbose)
  1. Extract the short hash and append it to each entry for traceability
  2. Skip merge commits (Merge branch, Merge pull request)
  3. Insert the new section at the top of CHANGELOG.md, below the header — never overwrite existing entries
  4. If no CHANGELOG.md exists, create it with the standard Keep a Changelog header
  5. With --dry-run, print to stdout only — do not write to file
  6. After writing, confirm with the user and suggest git add CHANGELOG.md

Quality Gate

  • If fewer than 2 commits are found in the range, warn the user before generating
  • If breaking changes are detected (feat!, BREAKING CHANGE footer), highlight them prominently
  • Never infer a version number from non-semver tags — ask the user to provide --version

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.