Backend changelog

Understand auto-generated changelogs via semantic-release. Use when viewing release history, understanding changelog format, or debugging missing changelog entries.

install

source · Clone the upstream repo

git clone https://github.com/sgcarstrends/sgcarstrends

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/sgcarstrends/sgcarstrends "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.claude/skills/changelog" ~/.claude/skills/sgcarstrends-backend-changelog && rm -rf "$T"

manifest: .claude/skills/changelog/SKILL.md

source content

Changelog Skill

Changelogs are auto-generated by

@semantic-release/changelog

on each release.

How It Works

semantic-release runs on push to
```
main
```
```
@semantic-release/release-notes-generator
```
generates notes from commits (conventionalcommits preset)
```
@semantic-release/changelog
```
prepends notes to
```
CHANGELOG.md
```
```
@semantic-release/git
```
commits the updated changelog

Changelog Sections

Commit types map to changelog sections:

Commit Type	Changelog Section
`feat`	Features
`fix`	Bug Fixes
`perf`	Performance Improvements
`revert`	Reverts
`feat!` / `BREAKING CHANGE`	BREAKING CHANGES

Types

chore

docs

refactor

test

ci

do not appear in the changelog.

Viewing Changelog

# View the changelog file
cat CHANGELOG.md

# View a specific GitHub release's notes
gh release view v4.46.0

# List recent releases with dates
gh release list --limit 10

Missing Changelog Entry?

If a commit does not appear in the changelog:

Check the commit type — only
```
feat
```
,
```
fix
```
,
```
perf
```
,
```
revert
```
generate entries
Verify the commit landed on
```
main
```
(not a feature branch)
Check if semantic-release ran:
```
gh run list --workflow=release.yml
```
Ensure commit message follows conventional format

File Location

Changelog:
```
CHANGELOG.md
```
(root of repository)

Config:

.releaserc.json

→

@semantic-release/changelog

plugin

See
```
conventional-commits
```
skill for commit message format
See
```
release-management
```
skill for release workflow