dom-release-notes-for-humans
Skill7 starsChanged 4 days agoMITView on GitHub
Use whenever `release-notes-for-humans` applies.
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- auditSkill
- harmonizeSkill
- shell-integrationSkill
- agent-task-directoriesSkill
- agent-task-relaySkill
- agent-documentationSkill
- prepushSkill
- skill-developmentSkill
- super-reviewSkill
- vitest-conventionsSkill
- dom-sensible-commit-flowSkill
- dom-sensible-contribution-flowSkill
- fish-shell-scriptingSkill
- human-facing-writingSkill
- intentional-dependency-choiceSkill
- posix-shell-scriptingSkill
- refine-agent-workflowSkill
- release-notes-for-humansSkill
- sensible-commit-flowSkill
- sensible-contribution-flowSkill
- simple-github-cliSkill
- subagent-review-flowSkill
- verify-findingsSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
When the base workflow needs a default evidence scope, use the current repository and local HEAD as the target, including commits that …
- Very specific: line 35
Use * for every unordered release note bullet.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Release Notes
Public Workflow
For every invocation, load release-notes-for-humans and follow its complete workflow. This overlay adds scope and delivery defaults, release version recommendations, bullet rendering, and package links below. Apply the global Explicit user direction policy to task-scoped overrides of this overlay’s procedure and presentation conventions.
Workflow Defaults
Apply these defaults and constraints within the base workflow:
- When the base workflow needs a default evidence scope, use the current repository and local
HEADas the target, including commits that haven’t been pushed to a remote. Exclude uncommitted changes unless explicitly requested. - Apply the presentation conventions.
- When drafting or editing without a file target, default to ready-to-paste changelog Markdown. Present approval proposals and questions, decisions requiring review, required disclosures, material evidence limitations, and applicable release version recommendations separately from the changelog Markdown. Omit other commentary. Use the base workflow’s delivery for file edits and read-only reviews. Drafting alone doesn’t authorize file changes or submission.
Release Version Recommendations
When drafting or editing notes for a non-initial release that hasn’t been published, recommend a version for each release unit without an assigned version when the evidence permits. If a version is already assigned, report any material mismatch with the evidence or versioning policy instead of proposing a replacement. Follow the project’s versioning policy, including its rules for versions below 1.0.0, prereleases, and synchronized packages. For stable releases using Semantic Versioning, recommend the smallest version increment that covers the most significant verified change: major for incompatible changes, minor for compatible additions or public API deprecations, or patch for compatible fixes.
Give the release type and a brief rationale. Include an exact next version only when the previous release version and applicable policy are established. When a limited evidence scope or unclear policy prevents a firm recommendation, state that limitation or qualify the recommendation instead of implying a complete release assessment.
Deliver the recommendation after the changelog Markdown or in the response accompanying a file edit, outside the release note itself. A recommendation doesn’t select or change the release version. In read-only reviews, discuss versioning only when it supports a concrete finding under the base workflow’s review contract.
Presentation Conventions
- In release note prose outside headings, apply the package link map to package names.
- Use
*for every unordered release note bullet. If a generic Markdown formatter’s only disagreement is normalizing this marker to-, preserve*and don’t treat the marker-only result as a release note failure.
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.

