Skip to content
Back to skills

Changelog Generator

ASecurity

Parse Git commit logs to generate a CHANGELOG.md adhering to Conventional Commits.

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 27, 2026
developmentbashangularnodegitapi

Works with

  • cli
  • api

Security analysis

A92/100
  • mediumInstalls packages at runtime which could introduce malicious dependencies

Pro shows the line behind each finding and how to fix it

Scanned September 27, 2026

npx -y skills add RMAzrim/opencode-artes --skill changelog-generator --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Changelog Generator?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Changelog Generator
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rmazrim-changelog-generator/badge)](https://www.skillsdirectory.com/skills/rmazrim-changelog-generator)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: Changelog Generator
description: Parse Git commit logs to generate a CHANGELOG.md adhering to Conventional Commits.
metadata:
  source: skills/changelog-generator/changelog-generator.md
---

# Changelog Generator

## Prerequisites & Dependencies
- Git repository with Conventional Commits (`feat:`, `fix:`, `feat!:` / `BREAKING CHANGE:` …)
- `git-cliff` 2.x or Node 18+ with `npm i -D conventional-changelog-cli`
- Semantic tags present (`vX.Y.Z`) marking release boundaries

## Execution Steps
1. Validate history hygiene: list non-conventional commits since the last tag (`git log $(git describe --tags --abbrev=0)..HEAD --oneline`) and fix noteworthy ones via rebase before generating.
2. Determine the next version from commit types: breaking → major, `feat` → minor, only `fix`/`chore` → patch.
3. Generate the changelog since the last tag with the chosen tool, mapping types to sections (Features / Bug Fixes / Breaking Changes).
4. Prepend the new section at the top of the existing CHANGELOG.md and edit or regenerate the `[Unreleased]` link references.
5. Review output wording: remove noise commits (chore: bump deps), link to issues/PRs, and reorder breaking changes up front.
6. Commit `CHANGELOG.md`, create the release tag, and derive GitHub Release notes from the same section.

```bash
git log "$(git describe --tags --abbrev=0)..HEAD" --oneline --no-merges

# git-cliff (config: cliff.toml)
git cliff --tag v1.4.0 --prepend CHANGELOG.md

# conventional-changelog
npx conventional-changelog -p angular -i CHANGELOG.md -s -r 0
```

## Output Example

```markdown
## [1.4.0] - 2026-09-09
### Breaking
- api: remove deprecated /v1/login endpoint (#312)
### Features
- orders: support bulk cancellation (#305)
### Bug Fixes
- payments: retry idempotent charges on gateway timeout (#318)
```
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.