agentleFS
everpcpceverpcpc/KMReader/.agents/skills/changelog/SKILL.md

changelog

Skill118 starsChanged 7 days agoMITView on GitHub

Generate App Store changelog text from commits between the latest tag and HEAD. Use full commit details, keep user-facing language, sectioned plain text, and exclude technical implementation details.

165 other projects use a version of this.

Adopted by

Most recently taken up by

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.
  • CoralGameSkill

    playtest-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

  • lilangMaxSkill

    soak-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

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 154 edited versions we read keep these.

  • 8

    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
  1. Very specific:

    Use commits from the latest tag to HEAD.

    line 18
  2. Distinctive:

    If no tag exists, use full history and state that assumption.

    line 25
  3. Distinctive:

    Read detailed commit bodies, not only commit titles.

    line 33
  4. Distinctive:

    Write for end users in friendly, clear product language.

    line 34
  5. Distinctive:

    Do not include emoji.

    line 37
  6. Distinctive:

    Do not include technical implementation details.

    line 38
  7. Distinctive:

    Remove internal terms, file names, class names, and refactor-only details.

    line 44
  8. Distinctive:

    Keep each bullet concise and meaningful.

    line 45
  9. Distinctive:

    Default output is changelog text only.

    line 49
  10. Very specific:

    If the user asks to update a file, write the final content to APP_STORE_CHANGELOG.txt.

    line 51

“Common” is measured: kept by at least 6 in 10 of the 154 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

Changelog

Generate App Store changelog content for end users.

When To Use

  • The user asks for a release changelog.
  • The user asks to summarize recent changes for App Store update notes.
  • The task is to convert git commits into user-facing release notes.

Source Range

Use commits from the latest tag to HEAD.

latest_tag=$(git describe --tags --abbrev=0)
git log "${latest_tag}..HEAD" --pretty=format:'%H%n%s%n%b%n---'

If no tag exists, use full history and state that assumption.

git log --pretty=format:'%H%n%s%n%b%n---'

Content Rules

  • Read detailed commit bodies, not only commit titles.
  • Write for end users in friendly, clear product language.
  • Organize output into sections.
  • Output plain text only, optimized for copy.
  • Do not include emoji.
  • Do not include technical implementation details.

Writing Style

  • Focus on user-visible improvements and behavior changes.
  • Merge related commits into one coherent item.
  • Remove internal terms, file names, class names, and refactor-only details.
  • Keep each bullet concise and meaningful.

Output

Default output is changelog text only.

If the user asks to update a file, write the final content to APP_STORE_CHANGELOG.txt.

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.