MicrosoftKnown publishermicrosoft/frontier-ghcp-ttt-rvas/sessions/session-m3-05-agent-skills/lab/solution/release-notes/SKILL.mdrelease-notes
Skill3 starsChanged 2 months agoMITView on GitHub
Write release notes or a CHANGELOG entry from a list of merged pull requests. Use when the user asks for release notes, a changelog entry, "what shipped", or a version summary, even if they don't name the format. Don't use for commit messages, PR descriptions, or marketing copy.
181 other projects use a version of this.
Adopted by
Most recently taken up by
- lengrufeng2008/dsh-skill-librarytheir own version, first seen Nov 15, 2026
- VladButacu/agentkittheir own version, first seen Nov 15, 2026
- binay-py/claude-skillstheir own version, first seen Nov 15, 2026
- viscouslofi/wolfpacktheir own version, first seen Nov 15, 2026
- WireCatLabs/wirecat-desktoptheir own version, first seen Nov 15, 2026
- ychampion/ystacktheir own version, first seen Nov 15, 2026
Used with
Projects with it also use brainstorm-experiments-existing, brainstorm-ideas-new 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.
skytiger6724Skillbrainstorm-experiments-existing
Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
Also in 6 projects that use this
- skytiger6724Skill
brainstorm-ideas-new
Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.
Also in 6 projects that use this
45ckSkillpestle-analysis
Also in 6 projects that use this
About-IntelligenceSkillpositioning-ideas
Brainstorm product positioning ideas differentiated from competitors.
Also in 6 projects that use this
- About-IntelligenceSkill
product-name
Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience.
Also in 6 projects that use this
- +7 more from skytiger6724
Other versions181 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 181
- tw93/Mole★ 75ksame name
- makeplane/plane★ 62ksame name
- tabler/tabler★ 42ksame name
- pnpm/pnpm★ 37ksame name
- quasarframework/quasar★ 27ksame name
- dotnet/core★ 22ksame name
- zauberzeug/nicegui★ 16ksame name
- adobe/react-spectrum★ 16ksame name
- espanso/espanso★ 15ksame name
- formbricks/formbricks★ 13ksame name
171 more not listed
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 repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- sessions/session-m2-01-copilot-cli/lab/solution/agent-tasks/.github/copilot-instructions.mdCopilot instructions
- sessions/session-m2-03-spaces-and-context/lab/solution/.github/copilot-instructions.mdCopilot instructions
- sessions/session-m3-02-cloud-agent/lab/starter/copilot-instructions.mdCopilot instructions
- sessions/session-m4-02-iac-with-copilot/lab/solution/.github/copilot-instructions.mdCopilot instructions
- sessions/session-m4-02-iac-with-copilot/lab/starter/.github/copilot-instructions.mdCopilot instructions
- sessions/session-m5-03-hve-core-challenge/lab/solution/decision-api/.github/copilot-instructions.mdCopilot instructions
- baoyu-infographicSkill
- diagram-creatorSkill
- docxSkill
- excalidraw-diagramSkill
- humanize-contentSkill
- impeccableSkill
- pdfSkill
- pptxSkill
- rvap-brandSkill
- skill-creatorSkill
- xlsxSkill
- impeccableSkill
- session-format-validatorSkill
- grill-meSkill
- decision-interviewSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 167 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Write the entry the way the project's existing CHANGELOG.md does, so readers see one consistent style.
- Very specific: line 12
Read the top two entries of CHANGELOG.md.
- Distinctive: line 13
Read the list of merged PRs.
- Distinctive: line 15
Write one line per user-visible change, in plain words, ending with the PR number.
- Very specific: line 17
If any PR is labeled breaking, add it under Upgrade notes with what the reader must do.
- Distinctive: line 26
If the version number or release date is missing, ask.
“Common” is measured: kept by at least 6 in 10 of the 167 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.
Files
Release notes
Write the entry the way the project's existing CHANGELOG.md does, so readers see one consistent style.
Steps
- Read the top two entries of
CHANGELOG.md. Copy their structure and tone. - Read the list of merged PRs. Ask for it if you don't have one.
- Group PRs using references/format.md.
- Write one line per user-visible change, in plain words, ending with the PR number.
- Skip internal work: refactors, dependency bumps, typo fixes. Readers can't act on them.
- If any PR is labeled
breaking, add it under Upgrade notes with what the reader must do. - Insert the new entry above the previous one. Don't rewrite older entries.
Why these rules
The changelog is the one place users learn what changed. Noise buries the two lines they need, so keep only what changes their behavior. State the upgrade action explicitly because people skim for it.
Ask before guessing
If the version number or release date is missing, ask. Never invent one.
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
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.