write-changelog
Skill1.2k starsChanged 10 months agoMITView on GitHub
Write or update changelog entries with user-focused language
13 other projects use a version of this.
Trending
Quiet since May.thin dataabout the whole repository
Most recently taken up by
- Donchitos/Claude-Code-Game-Studiostheir own version, first seen Nov 15, 2026
- pahlevikun/levistacktheir own version, first seen Nov 1, 2026
- DataDog/dd-trace-rbtheir own version, first seen Oct 9, 2026
- petera2c/simple-tabletheir own version, first seen Oct 8, 2026
- classroomio/classroomiotheir own version, first seen Oct 8, 2026
- zulip/zuliptheir own version, first seen Oct 8, 2026
Who's talking about jamiebrynes7/obsidian-todoist-plugin
- Ledaryy/obsidian-todoist-completed-tasks“[Feature Request] Automatic task fetching”GitHub · Jan 15, 2023 · 2 reactions
- debuglevel/obsidian-tasks“Disable warnings about tasks in callouts”GitHub · May 29, 2026
- d-eniz/jupymd“fix: code blocks in pdf export”GitHub · Jan 16, 2026
- xhuajin/obsidian-tabs“[BUG] Certain Codeblocks Not Rendering Inside Tab”GitHub · Jul 27, 2024
The biggest 4 of 4 mentions linking to the repository that our crawl found. Each line is their own headline.
Used with
Projects with it also use security-audit.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CloudflareSkillsecurity-audit
Security guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full/comprehensive/end-to-end reviews, or requested report artifacts.
Also in 3 projects that use this
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- zulip/zulip★ 26ksame name
- microsoft/vscode-pull-request-github★ 2.6ksame name
- classroomio/classroomio★ 1.7ksame name
- DataDog/dd-trace-rb★ 419same name
- petera2c/simple-table★ 235same name
- kannandreams/agent-top★ 22same name
- plugyawn/armada★ 2same name
- wsm94/gi-claude-skills★ 2same name
- fabianmagrini/skills★ 1same name
3 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 repository4 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- plugin/CLAUDE.mdCLAUDE.md
- write-git-commitSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Write or update changelog entries following these guidelines:
- Very specific: line 31
Always add new entries to the ## Unreleased section at the top of the changelog.
“Common” is measured: kept by at least 6 in 10 of the 13 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.
Files
Changelog
Write or update changelog entries following these guidelines:
Guidelines
- Focus on user benefits rather than implementation details
- Keep entries concise - typically a single line without subpoints
- Emphasize what the user can now do or how their experience improves
- Avoid technical specifics like state management, CSS classes, or internal architecture
Categories
Entries are organized under these category headings:
### ✨ Features- New functionality for users### 🐛 Bug Fixes- Corrections to existing behavior### 🔁 Changes- Modifications to existing features### ⚙ Internal- Technical changes (use sparingly, still user-focused)### 🌐 Translations- New or updated translations### Breaking changes- For major releases only### Deprecated- Features being phased out
Unreleased Section
Always add new entries to the ## Unreleased section at the top of the changelog. Create the appropriate category heading if it doesn't exist yet. Entries are moved to a versioned section during the release process.
Examples
Good:
- "Added keyboard shortcuts for common actions"
- "Tasks now sync automatically when Obsidian starts"
- "Fixed tasks not appearing after editing"
Bad:
- "Refactored TaskStore to use Redux pattern with selectors"
- "Added
useEffecthook to trigger sync on mount" - "Fixed CSS specificity issue in task-list component"
Location
The changelog is located at docs/docs/changelog.md.
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
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.

