agentleFS
y-miyazakiy-miyazaki/config/.claude/skills/changelog/SKILL.md

changelog

Skill1 starsChanged 3 days agoApache-2.0View on GitHub

Survey and update CHANGELOG.md from unreleased commits and undocumented releases. Use in conversation when the user asks to check, review, or update the changelog. Also the loop entry skill when automation supplies commit/release detect JSON. Interactive default is survey only; edit CHANGELOG.md when the request asks for changes to be made (for example fix, apply, or update) or automation sets agent_edit_allowed in Constraints.

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 13 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 10 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 10 projects that use this

  • CoralGameSkill

    team-audio

    Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.

    Also in 13 projects that use this

  • +6 more from lilangMax
  • +2 more from CoralGame

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 154 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create CHANGELOG.md from the Keep a Changelog template when changelog_exists is false and edits are allowed

    line 34
  2. Distinctive:

    Create git tags or cut releases in CI outside the changelog file

    line 41
  3. Distinctive:

    Run detection when the caller already supplied complete detect JSON (automation path)

    line 42
  4. Distinctive:

    When intent is unclear, survey and offer to apply — edits are harder to undo than a report.

    line 67
  5. Very specific:

    When agent_edit_allowed is true, resolve agent_edit_target: on the interactive path use fix (this skill).

    line 69
  6. Very specific:

    IF detect reports skip OR both commits and releases are empty after gathering → emit survey no-op per common-output-format.md (Overview …

    line 73
  7. Very specific:

    IF agent_edit_allowed is false → emit survey shape with ### Candidates.

    line 75

“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

UTILITY SKILL — changelog survey and patch, not release tagging.

Input

  • Interactive (required): natural-language request; optional scope (all, or range with --since) — constraints in ## Constraints or category-scope.md
  • Automation (optional): detect JSON in prompt — from a caller or optional skill detect script; not required for interactive runs. Read agent_edit_allowed and agent_edit_target from ## Constraints per category-automation-envelope.md

Path allowlist, when present, arrives in ## Constraints.

Output Specification

Changelog report per common-output-format.md. Survey shape when changelog_file is not edited; apply shape when edited — within category-scope.md.

Execution Scope

USE FOR:

  • Survey unreleased commits and undocumented releases; emit Candidates under ## [Unreleased]
  • Create CHANGELOG.md from the Keep a Changelog template when changelog_exists is false and edits are allowed
  • Group detect commits[] into Keep a Changelog sections under ## [Unreleased]
  • Promote detect releases[] into ## [x.y.z] - date sections and move matching bullets out of ## [Unreleased]
  • Preserve existing released version sections and formatting

DO NOT USE FOR:

  • Create git tags or cut releases in CI outside the changelog file
  • Run detection when the caller already supplied complete detect JSON (automation path)

Reference Files Guide

  • common-checklist.md (always read)
  • common-output-format.md (always read)
  • category-scope.md (always read)
  • category-detect-scope.md (read on interactive path)
  • category-input-schema.md (read when detect JSON is present or the optional detect script is run)
  • category-automation-envelope.md (read on automation path)
  • common-troubleshooting.md (read on failure)
  • category-pr-body-links.md (read when synthesizing the PR body)
  • assets/pr-body-template.md and assets/pr-body-template-survey.md (read when synthesizing the PR body)

Workflow

Resolve agent_edit_allowed before mapping commits:

Sourceagent_edit_allowed
Interactive — default: the request asks to look, check, triage, or survey, or only names the skillfalse — survey only; do not edit changelog_file
Interactive — the request asks for changes to be made (for example fix, apply, 修正して, 適用して, update, add)true
Interactive — follow-up after a survey asking to applytrue
Automation — ## Constraintsagent_edit_allowed: true or agent_edit_allowed: false from category-automation-envelope.md

When intent is unclear, survey and offer to apply — edits are harder to undo than a report.

When agent_edit_allowed is true, resolve agent_edit_target: on the interactive path use fix (this skill); on the automation path read agent_edit_target from ## Constraints. Do not branch on other caller metadata outside ## Constraints.

  1. Resolve scope (category-scope.md). Parse detect JSON when present; otherwise resolve the detect universe from the prompt (category-detect-scope.md), run this skill's optional detect script with the resolved --scope (default all), then Agent-complement beyond mechanical output; if tools for detect are unavailable, gather commits/releases from the user request and repository tools instead of silent no-op. Load category-input-schema.md when parsing detect output. On detect script non-zero exit, read stdout and stop.
  2. On the automation path, read category-automation-envelope.md for Constraints, PR templates, and Session Metrics.
  3. IF detect reports skip OR both commits and releases are empty after gathering → emit survey no-op per common-output-format.md (Overview explains no-op); on automation path append ## Session Metrics per category-automation-envelope.md; stop.
  4. Map commits and releases per common-checklist.md.
  5. IF agent_edit_allowed is false → emit survey shape with ### Candidates; on automation path load assets/pr-body-template-survey.md at synthesis and append ## Session Metrics per category-automation-envelope.md; stop — do not edit changelog_file.
  6. ELSE IF agent_edit_allowed is true AND agent_edit_target is not fix → emit survey shape; note expected agent_edit_target: fix in Overview; stop — do not edit changelog_file.
  7. ELSE (agent_edit_allowed is true AND agent_edit_target is fix) → edit only changelog_file per category-scope.md; emit apply shape with ### Changes and ## Verification; on automation path load assets/pr-body-template.md at synthesis and append ## Session Metrics per category-automation-envelope.md.

Error Handling

ConditionSeverityAction
Detect script non-zero exit or status: "error" (when invoked)FatalRead stdout; stop — do not treat as success-path detect JSON
skip or empty commits/releasesInfoEmit survey no-op (Overview explains no-op); stop
changelog_file outside scopeRecoverableDefer; note in report
Edit requested but ## Constraints set agent_edit_allowed: falseInfoSurvey only; note that the caller Constraints disallow edits
agent_edit_allowed true with agent_edit_target not fixRecoverableSurvey only; note expected agent_edit_target: fix
changelog_exists false and agent_edit_allowed is trueRecoverableCreate Keep a Changelog template, then add bullets

Examples

  • Prompt: Survey CHANGELOG gaps from unreleased commits
  • Result: Survey report per references/common-output-format.md; edit changelog_file only when agent_edit_allowed is true.

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.