changelog
Skill4 starsChanged 6 months agoApache-2.0View on GitHub
Auto-generate changelog from git commits — grouped by feat/fix/docs with PR links
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 142 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Run in your repo. Reads commits since last tag, groups by type: ✨ Features / 🐛 Bug Fixes / 📝 Docs / ♻️ Refactoring / 🧪 Tests
“Common” is measured: kept by at least 6 in 10 of the 142 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
Auto-generate changelog from git commits.
How to use
Run in your repo. Reads commits since last tag, groups by type: ✨ Features / 🐛 Bug Fixes / 📝 Docs / ♻️ Refactoring / 🧪 Tests
Works best with conventional commits (feat:, fix:, docs:, etc.).
For full instructions, read agents/changelog.md.
Other versions152 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 152
- 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.4ksame name
- UnigramDev/Unigram★ 5.5ksame name
- entireio/cli★ 5.3ksame name
142 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.
Used alongsideProjects with it also use soak-test, team-live-ops 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.
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
lilangMaxSkillteam-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
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
CoralGameSkillteam-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
In this repository54 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/code-review.mdcCursor rule
- .cursor/rules/db-design.mdcCursor rule
- .cursor/rules/debug.mdcCursor rule
- .cursor/rules/django-forge.mdcCursor rule
- .cursor/rules/dotnet-forge.mdcCursor rule
- .cursor/rules/flutter-forge.mdcCursor rule
- .cursor/rules/nestjs-forge.mdcCursor rule
- .cursor/rules/neuraforge.mdcCursor rule
- .cursor/rules/pr-review.mdcCursor rule
- .cursor/rules/react-forge.mdcCursor rule
- .cursor/rules/refactor.mdcCursor rule
- .cursor/rules/rn-forge.mdcCursor rule
- .cursor/rules/scaffold.mdcCursor rule
- .cursor/rules/spring-forge.mdcCursor rule
- .cursor/rules/test-forge.mdcCursor rule
- api-designSkill
- api-testingSkill
- architecture-reviewSkill
- codebase-graphSkill
- code-reviewSkill
- db-designSkill
- debugSkill
- deps-auditSkill
- design-syncSkill
- devils-advocateSkill
- devopsSkill
- django-forgeSkill
- doc-generatorSkill
- documentationSkill
- domain-setupSkill
- dotnet-forgeSkill
- explainSkill
- feature-pipelineSkill
- flutter-forgeSkill
- fullstack-orchestratorSkill
- git-worktreesSkill
- load-testingSkill
- migrateSkill
- nestjs-forgeSkill
- performance-reviewSkill
- presentation-builderSkill
- product-managerSkill
- pr-reviewSkill
- react-forgeSkill
- refactorSkill
- rn-forgeSkill
- scaffoldSkill
- security-reviewSkill
- spring-forgeSkill
- test-forgeSkill
- ui-validationSkill
- video-creatorSkill
- workspace-protocolSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

