ship-notes
Skill0 starsChanged 16 days agoMITView on GitHub
Write changelog or release notes from the real commit range. Use when the user asks for a changelog, release notes, version summary, or what shipped. Do not invent commits or claims the diff does not support.
2 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- rpraharaj/ai-engineeredited, first seen Nov 1, 2026
- jeana-adhoc/claude-skillstheir own version, first seen Jun 26, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- rpraharaj/ai-engineer★ 111% same
Wrote their own version · 1
- jeana-adhoc/claude-skills★ 1same 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 repository66 other files it gives its agents.
- AGENTS.mdAGENTS.md
- a11y-passSkill
- assess-changeSkill
- build-regression-packSkill
- charter-exploratorySkill
- classify-dataSkill
- commitSkill
- cut-releaseSkill
- data-changeSkill
- debugSkill
- design-experimentSkill
- diff-environmentsSkill
- draft-steercoSkill
- engineering-barSkill
- explain-codeSkill
- explore-codebaseSkill
- fix-ciSkill
- handoffSkill
- implement-changeSkill
- incident-triageSkill
- lean-reviewSkill
- map-dependenciesSkill
- map-design-handoffSkill
- map-processSkill
- open-prSkill
- performanceSkill
- plan-data-migrationSkill
- plan-incrementSkill
- plan-rollbackSkill
- plan-uatSkill
- prioritize-backlogSkill
- production-passSkill
- ready-to-mergeSkill
- record-decisionSkill
- refactor-safelySkill
- revert-changeSkill
- review-architectureSkill
- review-changeSkill
- review-pipelineSkill
- security-passSkill
- shape-workSkill
- spec-analyticsSkill
- spec-observabilitySkill
- start-projectSkill
- synthesize-discoverySkill
- triage-blockersSkill
- triage-defectSkill
- update-raidSkill
- verify-uiSkill
- write-api-examplesSkill
- write-architectureSkill
- write-designSkill
- write-dev-tasksSkill
- write-docsSkill
- write-integration-contractSkill
- write-nfrSkill
- write-opportunitySkill
- write-prdSkill
- write-requirementsSkill
- write-runbookSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- Distinctive: line 31
If this is not a git repo or the range is empty, stop.
- Distinctive: line 44
Do not mention agents or “generated by.”
≈ “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.
Files
Ship notes
Describe what actually shipped. Source of truth is the commit range.
Is this the right skill?
| Signal | Do this instead |
| Tag / publish / deploy | cut-release after notes |
| Why we chose X | record-decision |
Required inputs
- Git range (default: last version tag → HEAD)
- Existing changelog format if the repo has one
If this is not a git repo or the range is empty, stop.
Human decisions (do not invent)
- Version bump (only if they asked)
- Performance/security wins not in the commits
Procedure
git log/git diff --staton the range.- Detect format:
CHANGELOG.md/ fragments / host release body / reply-only Added/Changed/Fixed. - Match heading, date, and version prefix from the last entry. Do not switch formats.
- User-facing first. Drop typo-only commits. Call out breaking changes and migrations from the diff /
data-changeplans. - Do not mention agents or “generated by.”
Output
- Path: existing changelog or the reply
- Template: references/notes-template.md
Quality bar
- Range named
- No invented features or metrics
- Breaking/migration called out or n/a
Done
Range, path, whether you bumped a version. Next: commit or cut-release.
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.