agentleFS
divysharma-codedivysharma-code/Skills/release-notes-writer/SKILL.md

release-notes-writer

Skill1 starsChanged 21 days agoNo licenceView on GitHub

Write Cohere release notes for Ops, PlatCon, and CX/Client Services readers — internal, non-engineering — from a Jira ticket, a Confluence config-doc page, or a rough bullet list of what shipped. Turns a technical config/feature change into a note that answers what changed, why, how it affects the reader's day-to-day, and what they need to do differently; personality/human tone is welcome since the audience is internal, but never at the cost of clarity or burying the actual change. Use when Divy asks to write, draft, or publish release notes, a "what shipped" update, a change announcement for Ops/CX/PlatCon, or wants to turn a ticket or config doc into a release note.

11 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.