add-to-changelog
Skill2 starsChanged 15 days agoMITView on GitHub
Add a new entry to the project's CHANGELOG.md following the Keep a Changelog format and Semantic Versioning. Use when the user asks to "add a changelog entry", "update the changelog", "log this change", or runs /add-to-changelog with a version, change type, and message. Creates CHANGELOG.md if missing, adds the entry under the right version + change-type section, and keeps formatting consistent.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- drvoss/everything-copilot-clitheir own version, first seen Oct 26, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- drvoss/everything-copilot-cli★ 49same name
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 repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- cmux-agent-orchestratorSkill
- cmux-pr-qc-agentSkill
- cmuxSkill
- finchSkill
- peekSkill
- gmail-inbox-zero-triageSkill
- gmail-oib-zeroSkill
- whatsapp-triageSkill
- check-prSkill
- cli-reviewSkill
- coderabbit-requestSkill
- convex-domain-folderSkill
- e2e-remote-setupSkill
- greploopSkill
- update-docsSkill
- antigravity-cliSkill
- social-captureSkill
- check-model-usageSkill
- code-structureSkill
- evidence-driven-testingSkill
- interviewSkill
- issue-breakdownSkill
- linear-labelsSkill
- model-classifierSkill
- remotion-explainer-videoSkill
- skill-makerSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 3 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Add a new entry to the project's CHANGELOG.md following the Keep a Changelog format and Semantic Versioning.
- Distinctive: line 23
If any argument is missing, infer sensible values from context (e.g.
- Very specific: line 28
Check if CHANGELOG.md exists in the project root.
- Very specific: line 37
Look for an existing ## [<version>] section.
- Very specific: line 38
If it exists, add the entry under the appropriate ### <Change Type> heading (create the heading if absent).
- Very specific: line 39
If it doesn't, create a new version section with today's date: ## [<version>] - YYYY-MM-DD (get the date from date +%F), then the …
- Distinctive: line 40
Keep versions in reverse-chronological order and entries tidy.
- Distinctive: line 41
Write the file back.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Add to Changelog
Add a new entry to the project's CHANGELOG.md following the Keep a Changelog format and Semantic Versioning.
Arguments
<version>— SemVer version (e.g.1.1.0,2.0.0-beta.1)<change_type>— one of:added,changed,deprecated,removed,fixed,security<message>— description of the change (quote multi-word messages)
If any argument is missing, infer sensible values from context (e.g. the current work) or ask the user.
Process
- Parse the version, change type, and message from the arguments.
- Check if
CHANGELOG.mdexists in the project root. If not, create it with the standard Keep a Changelog header:# Changelog All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/), and this project adheres to [Semantic Versioning](https://semver.org/). - Look for an existing
## [<version>]section.- If it exists, add the entry under the appropriate
### <Change Type>heading (create the heading if absent). - If it doesn't, create a new version section with today's date:
## [<version>] - YYYY-MM-DD(get the date fromdate +%F), then the change-type heading and entry.
- If it exists, add the entry under the appropriate
- Keep versions in reverse-chronological order and entries tidy.
- Write the file back.
Change types
- Added — new features
- Changed — changes to existing functionality
- Deprecated — soon-to-be-removed features
- Removed — removed features
- Fixed — bug fixes
- Security — security fixes
Example
/add-to-changelog 1.1.0 added "Waitlist referral source configuration" →
## [1.1.0] - 2026-01-15
### Added
- Waitlist referral source configurationDoes 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
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.

