changelog
Skill3 starsChanged 36 days agoMITView on GitHub
Generate a concise, user-facing changelog from meaningful changes in the current repository and branch. Use when the user asks for a changelog, release notes, recent changes, or a summary of work over a date range or contributor scope.
160 other projects use a version of this.
Adopted by
Most recently taken up by
- morethanwords/twebtheir own version, first seen Nov 9, 2026
- 27Aaron/skillstheir own version, first seen Nov 8, 2026
- computerlovetech/skillstheir own version, first seen Nov 8, 2026
- ainurdev/mystical-assistanttheir own version, first seen Nov 8, 2026
- RodrigoAnciaes/golem-sddtheir own version, first seen Nov 8, 2026
- itsryanarmani/skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use playtest-report, soak-test and 10 more.
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.
CoralGameSkillplaytest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
Also in 12 projects that use this
lilangMaxSkillsoak-test
Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.
Also in 9 projects that use this
- lilangMaxSkill
team-live-ops
Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.
Also in 9 projects that use this
- CoralGameSkill
team-polish
Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.
Also in 14 projects that use this
- +5 more from lilangMax
- +3 more from CoralGame
Other versions160 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 160
- meteor/meteor★ 45ksame name
- Donchitos/Claude-Code-Game-Studios★ 27ksame name
- MaaAssistantArknights/MaaAssistantArknights★ 24ksame name
- pipecat-ai/pipecat★ 17ksame name
- elie222/inbox-zero★ 13ksame name
- hashicorp/terraform-provider-aws★ 11ksame name
- JetBrains/ideavim★ 10ksame name
- BuilderIO/agent-native★ 7.6ksame name
- UnigramDev/Unigram★ 5.5ksame name
- entireio/cli★ 5.3ksame name
150 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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- audit-project-rulesSkill
- do-subtasksSkill
- pest-arch-reviewSkill
- qaSkill
- retroSkill
- simplify-agent-instructionsSkill
- to-prSkill
- to-subtasksSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 5 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 149 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Do not prompt the user for the date range or contributor scope when they are not provided.
- Very specific: line 22
If GitHub identity is needed for API resolution, identify the current GitHub user with gh api user --jq .login.
- Distinctive: line 29
When the default GitHub-user filter cannot be reliably matched to local author names or emails, use the repository commit API to resolve …
- Distinctive: line 32
Read relevant diffs and group duplicate or related commits into one change.
- Very specific: line 40
Start each bullet with one of: - Added, - Improved, or - Fixed.
- Distinctive: line 41
Write one meaningful change per bullet in plain language.
- Distinctive: line 46
Do not invent benefits or details that are not supported by the history.
- Very specific: line 47
If no meaningful changes match, return - No meaningful changes found.
“Common” is measured: kept by at least 6 in 10 of the 149 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
Quick start
Generate changelog text only. Do not create or edit a changelog file.
Do not prompt the user for the date range or contributor scope when they are not provided. Default to the past 7 days and the current Git user. Use the user's explicit date range and contributor scope when provided. Keep the default repository and branch as the current repository and current branch.
Workflow
- Identify the current Git user from the repository configuration and history.
If GitHub identity is needed for API resolution, identify the current GitHub
user with
gh api user --jq .login. - Identify the current repository and branch from the local git checkout.
- Inspect matching local history with
git logandgit show, including both regular commits and merge commits. Restrict results to the selected dates, branch, and contributor scope. When no date range is specified, use the previous 7 days; when no contributor is specified, use the current Git user. - When the default GitHub-user filter cannot be reliably matched to local author names or emails, use the repository commit API to resolve that GitHub login to commit SHAs, then inspect those commits with local git.
- Read relevant diffs and group duplicate or related commits into one change.
- Translate implementation details into meaningful outcomes a layman can understand. Include internal work only when it has a clear user, maintainer, documentation, reliability, or future-feature impact.
Output rules
- Return only a simple bullet list, with no preamble, table, or commit log.
- Start each bullet with one of:
- Added,- Improved, or- Fixed. - Write one meaningful change per bullet in plain language.
- Explain the result or benefit rather than copying commit messages.
- Combine commits that implement the same outcome.
- Omit routine formatting, mechanical refactors, tests, and dependency changes unless their impact is relevant enough to explain to others.
- Do not invent benefits or details that are not supported by the history.
- If no meaningful changes match, return
- No meaningful changes found.
Example output:
- Added clearer error messages when a saved report cannot be loaded.
- Improved the setup documentation for configuring GitHub authentication.
- Fixed an issue that could hide newly created projects from the project list.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.