agentleFS
MicrosoftKnown publishermicrosoft/dbt-fabricspark/.github/skills/generate-changelog/SKILL.md

generate-changelog

Skill72 starsChanged 5 months agoMITView on GitHub

Generate a succinct CHANGELOG.md entry from PR descriptions since the last version bump.

5 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions5 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 5

    1. danbooru/danbooru★ 2.9ksame name
    2. deepsense-ai/ragbits★ 1.7ksame name
    3. maslennikov-ig/claude-code-orchestrator-kit★ 248same name
    4. open-edge-platform/edge-ai-libraries★ 178same name
    5. dvy1987/agent-loom★ 4same name

    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 repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 4

    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
  1. Distinctive:

    If it does not exist, stop and tell the user:

    line 18
  2. Distinctive:

    Use past tense (e.g., "Added…", "Fixed…", "Improved…")

    line 52
  3. Distinctive:

    Do NOT include the full PR body text — summarize it

    line 54
  4. Distinctive:

    Keep the existing content intact below the new section.

    line 67

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

Generate Changelog

Produce a concise, user-facing changelog entry for the current version by summarizing merged PR descriptions.

Steps

  1. Check for the raw changelog — verify that .temp/VERSION_CHANGELOG_FULL.md exists in the repo root:

    test -f .temp/VERSION_CHANGELOG_FULL.md

    If it does not exist, stop and tell the user:

    The raw PR changelog has not been generated yet. Run this first:

    npm run get-version-diffs

    Then re-invoke this skill.

  2. Read the raw changelog — open .temp/VERSION_CHANGELOG_FULL.md. Each entry has the format:

    # <short sha>: <commit title>
    
    <PR description body>
    
    ---
  3. Filter out sentinel commits — skip any entry whose commit title matches the pattern ci: sentinel commit. These are CI verification commits with no user-facing changes.
  4. Read the current version — get the version string from:

    cat src/dbt/adapters/fabricspark/__version__.py

    The file contains a single line like version = "1.9.6". Extract the version number (e.g., 1.9.6).

  5. Summarize into a changelog entry — from the remaining (non-sentinel) PR descriptions, write a succinct changelog section. Follow these guidelines:

    • Group related changes under descriptive subheadings (e.g., ### Bug Fixes, ### New Features, ### Improvements)
    • Each item should be 1–2 sentences max — distill the PR description down to what matters to a user
    • Use past tense (e.g., "Added…", "Fixed…", "Improved…")
    • Reference PR numbers inline (e.g., (#42))
    • Do NOT include the full PR body text — summarize it
    • Match the style and depth of existing entries in CHANGELOG.md
  6. Prepend to CHANGELOG.md — insert the new section immediately below the # Changelog heading in CHANGELOG.md, above all existing version sections. The format is:

    ## v<version>
    
    <your summarized content>
    
    ---

    Keep the existing content intact below the new section.

  7. Report completion — show the user the new section you added and confirm the file was updated.

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.