agentleFS
Sign inStart free
cobusgreylingcobusgreyling/grok-bot-templates/skills/draft-changelog/SKILL.md

draft-changelog

Skill14 starsChanged 3 months agoMITView on GitHub

Paste this into Grok Bot after a successful run: Save the process we just used as a skill called “Draft Changelog”. A useful skill states the six fields from Skills and routines. Merged pull requests since the last tag must become user-facing release notes without Friday archaeology. Every entry maps to a merged PR or commit. No "various improvements" filler. Unpublished. Draft changelog markdown and a list of PRs omitted as internal, for the owner to restore if needed. Do…

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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:

    Call out anything that needs a migration note.

    line 25
  2. Distinctive:

    Every entry maps to a merged PR or commit.

    line 29
  3. Distinctive:

    Do not publish a GitHub release or tag.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Draft Changelog

Paste this into Grok Bot after a successful run:

Save the process we just used as a skill called “Draft Changelog”.

A useful skill states the six fields from Skills and routines.

1. When to use it

Merged pull requests since the last tag must become user-facing release notes without Friday archaeology.

2. Required inputs and access

  • GitHub repo
  • Previous tag or changelog heading
  • Audience (users vs operators)

3. Sequence of work

  1. List merged PRs since the last tag. Do not invent PRs.
  2. Group as breaking, added, fixed, or internal.
  3. Rewrite titles into user language. Keep PR numbers as links.
  4. Call out anything that needs a migration note.

4. How to validate the result

Every entry maps to a merged PR or commit. No "various improvements" filler. Unpublished.

5. What to return

Draft changelog markdown and a list of PRs omitted as internal, for the owner to restore if needed.

6. What requires approval

Do not publish a GitHub release or tag. Do not edit CHANGELOG.md on main without approval.

Type / in the composer to reference a saved skill. If it does not appear, open Settings → Plugins → Yours and enable it for this Bot.

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.

Check your setup, free