A release-note generator that reads Git commits since the latest version tag. Conventional commits are Git messages using labels such as “feat” for features and “fix” for bug fixes.

It is for preparing a release, generating release notes, or updating CHANGELOG.md, with an option to preview the result before writing it.

It removes the manual work of finding relevant commits and arranging them into a consistent changelog.

changelog — Skill for Claude Code by hamzaPixl

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add hamzaPixl/pixl-ai --skill changelog

Clone the repo

git clone --depth 1 https://github.com/hamzaPixl/pixl-ai

Made for: Claude Code.

Or install pixl-crew, the plugin that ships this one along with the rest of its 93 skills, 14 agents, 6 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/changelog/github.svg)](https://agentmods.dev/skills/hamzapixl/pixl-ai/changelog)

Your own site

<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/changelog"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/changelog/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/changelog"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/changelog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 676 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00053	$0.00676
Opus 5	$0.00026	$0.00338
Sonnet 5	$0.00011	$0.00135
Haiku 4.5	$0.00005	$0.00068

Measured 11d ago against content hash d7f47383930c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

changelog scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

packages/crew/skills/changelog/SKILL.md · 88 lines

How it starts

The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Overview

Parses conventional commits since the last git tag and generates a structured changelog entry. Supports dry-run mode for preview without writing.

Step 1: Determine Range

Find the latest tag: git describe --tags --abbrev=0 2>/dev/null
If --since <tag> is provided, use that instead
If no tags exist, use all commits on the current branch

Step 2: Parse Commits

Run git log <tag>..HEAD --pretty=format:"%H|%s|%an" --no-merges and parse each line:

Extract type from conventional commit prefix: feat, fix, refactor, chore, docs, test, perf, ci, style
Extract optional scope: feat(crew): ... → scope = crew
Extract description (everything after : )
Flag breaking changes: commits with ! after type/scope or BREAKING CHANGE: in body

For commits that don't follow conventional format, group under "Other".

Step 3: Group & Format

Generate markdown grouped by type:

## [version] — YYYY-MM-DD

### Breaking Changes
- **scope**: description (hash)

### Features
- **scope**: description (hash)

### Bug Fixes
- **scope**: description (hash)

### Refactoring
- description (hash)

### Other
- description (hash)

Type mapping:

Commit type	Section heading
`feat`	Features
`fix`	Bug Fixes
`refactor`	Refactoring
`perf`	Performance
`docs`	Documentation
`test`	Tests
`chore`	Maintenance
`ci`	CI/CD
`style`	Style

Omit empty sections. Use short hashes (7 chars).

Step 4: Detect Version

If pyproject.toml or package.json exists, read the current version. Otherwise use Unreleased as the version placeholder.

Step 5: Output

--dry-run (default): Print the changelog entry to stdout without writing
Otherwise: Prepend the entry to CHANGELOG.md (create if missing, preserve existing content below)

If the output path is specified via --output, write there instead.

Step 6: Summary

## Changelog Generated

- Range: <previous-tag>..HEAD
- Commits: N total (X features, Y fixes, Z other)
- Breaking changes: N
- Output: CHANGELOG.md (or dry-run)

Read the full file on GitHub · 88 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

11d ago First seen · 88 lines · 53 tokens per session scan A d7f47383930c

Subscribe to this mod's changes

changelog is a skill published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 4mo ago), licensed MIT. It adds 53 tokens to every session and 676 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Git and workflow Releases

agent-release-swarm

Agent skill for release-swarm - invoke with $agent-release-swarm.

ruvnet/ruflo · 19 tokens

release-announcement

Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.

paperclipai/paperclip · 42 tokens

multi-agent-release-manager

Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.

chromium/chromium · 27 tokens

release-notes

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

phuryn/pm-skills · 57 tokens

pack-submit

Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.

aeonfun/aeon · 27 tokens

updater_guide

Guidance for checking for and installing Row-Bot updates.

siddsachar/row-bot · 17 tokens