anchildress1anchildress1/awesome-github-copilot/skills/changelog-writer/SKILL.md

changelog-writer

Skill67 starsChanged 59 days agoMITView on GitHub

Rewrites changelog entries with cheeky, narrative flair following project conventions. Use this when asked to rewrite or update CHANGELOG.md entries.

21 other projects use a version of this.

Adopted by

Most recently taken up by

Sagargupta16/agent-recipestheir own version, first seen Nov 1, 2026
ommakes/Skillstheir own version, first seen Oct 27, 2026
maximhq/bifrosttheir own version, first seen Oct 20, 2026
WST2002/claude-code-skillstheir own version, first seen Oct 17, 2026
anchildress1/awesome-aiword for word, first seen Oct 13, 2026
mukundzha/clwstheir own version, first seen Oct 13, 2026

Used with

Projects with it also use regex-builder.

Other files people use alongside this one.

jMertaSkill
regex-builder
Use when the user asks to create, debug, explain, validate, or optimize a regular expression or replacement for a specific engine. Verifies representative matches, non-matches, captures, escaping, portability limits, and backtracking risk in the target runtime.
Also in 3 projects that use this

Other versions21 projects use a version of this.
Word for word · 1
anchildress1/awesome-ai★ 67100% same
Edited · 0
None found.
Wrote their own version · 20
maximhq/bifrost★ 9.4ksame name
jihe520/mindpocket★ 349same name
hamzafarooq/claude-code-starter★ 145same name
ommakes/Skills★ 21same name
zbruhnke/claude-code-starter★ 16same name
jaredpalmer/skills★ 8same name
carlkibler/agent-skills★ 6same name
kevinaimonster/skill-hub★ 4same name
Sagargupta16/agent-recipes★ 4same name
WST2002/claude-code-skills★ 4same name
10 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- eslint-plugin-configuringSkill
- generate-commit-messageSkill
- pr-comment-reviewSkill
- readme-generatorSkill
- test-writerSkill

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

0
Common
Most of the 18 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Read CHANGELOG.md first and match its established voice.
line 7
Distinctive:
Never neutralize the voice — it is the deliverable.
line 10
Distinctive:
No commit SHAs, PR numbers, or PR links below the version header.
line 88
Very specific:
Never touch CHANGELOG.md content outside the section being rewritten.
line 89

“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Read CHANGELOG.md first and match its established voice. The file's own precedent beats every rule below.

Never neutralize the voice — it is the deliverable.

Header

## [X.Y.Z](compare-url) (YYYY-MM-DD) emoji

GitHub compare link and ISO date are mandatory. Emoji picked for this release — reach for the obvious one only when nothing better fits. Repetition for emphasis (📡📡📡) is allowed.

Shape by release type

Release	Body
Single-fix patch	Quote + one narrative paragraph. No bullets.
Multi-change	Quote + `### Highlights` + closing paragraph
Any, with breaking changes	Add the Breaking Changes block before Highlights

Opening quote is always italicized inside a blockquote, and carries the mood.

Single-fix patch

## [0.1.4](https://github.com/ChecKMarKDevTools/rai-lint/compare/v0.1.3...v0.1.4) (2026-01-14) 🧹

> _Because even the tiniest version bump deserves a drumroll, or at least a polite cough._

A quick patch to fix the commitlint package version that was apparently auditioning for a game of hide-and-seek. No user-facing changes, just the machinery getting its act together.

Multi-change

## [0.1.3](https://github.com/ChecKMarKDevTools/rai-lint/compare/v0.1.2...v0.1.3) (2026-01-08) 📡📡📡

> _A boring release, in the best possible way:_ this one is about making CI/release automation less fragile and keeping dependencies current.

No user-facing rule behavior changes in either package. If you linted commits yesterday, you're linting commits today — just with fewer ways for the release machinery to hurt itself.

### Highlights

- **Release automation is harder to derail.** Release Please configuration and "single-tag" wiring were fixed so tags/versions line up cleanly across this monorepo instead of drifting into "wait, which package did we publish?" territory.
- **Security + supply chain posture got a tune-up.** The security audit workflow was improved, and the `astral-sh/setup-uv` action was bumped so the Python toolchain setup stays aligned with the ecosystem.

Highlights = bold claim, then plain-language impact. Never a bare verb phrase.

Breaking changes

State what broke · why · what the reader must do. Structure is identical across both tones; only the header changes.

Stable (≥ v1.0.0, non-prerelease) — emphatic, visually unmissable: **🚨 Breaking Changes (Yes, Really):** · **⚠️ The Part Where Things Break:**
Pre-v1 or prerelease — sardonic, because instability is the point: **Breaking Changes (Shocking, I Know):** · **Things That Changed Because v0.x Means 'Surprise Mechanics':**

Voice

Do:

Dry and blunt — "The release workflow decided that 'working' was negotiable."
Funny — "If this doesn't work, I'm learning pottery."
Impact over mechanism — "Release automation is harder to derail," not "fixed release config."
Own the failure — "prompting a debugging session I would describe as 'character-building'."

Never:

Enumerate commits (* commit abc123).
Corporate register — "We're excited to announce…"
Implementation archaeology in place of user impact.
Sanitize the personality out.

Hard constraints

No commit SHAs, PR numbers, or PR links below the version header.
Never touch CHANGELOG.md content outside the section being rewritten.
Breaking changes are never omitted, whatever the version.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free