agentleFS
Sign inStart free
Dafenxz0Dafenxz0/codex-maintainer-skills/prepare-release-brief/SKILL.md

prepare-release-brief

Skill2 starsChanged 5 months agoMITView on GitHub

Prepare maintainer release briefs from git history, diffs, changelogs, package metadata, or pull request lists. Use when Codex is asked to draft release notes, summarize changes since a tag, identify release risk, build a maintainer checklist, check version bumps, or create upgrade notes for an open-source project.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run scripts/commit_digest.py <range> when a local git repo and range are available.

    line 11
  2. Very specific:

    Read references/release-brief-template.md for the recommended output structure.

    line 13
  3. Distinctive:

    Call out release blockers, risky changes, missing tests, migration needs, and follow-up issues.

    line 15
  4. Distinctive:

    Keep release notes crisp and user-facing.

    line 26
  5. Distinctive:

    Do not list every commit unless the user asks for a raw changelog.

    line 27

≈ “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

Prepare Release Brief

Workflow

  1. Determine the release range: explicit git range, previous tag to HEAD, or user-provided PR/commit list.
  2. Run scripts/commit_digest.py <range> when a local git repo and range are available.
  3. Inspect package metadata, changelog, docs, tests, migrations, and public API changes touched in the range.
  4. Read references/release-brief-template.md for the recommended output structure.
  5. Separate user-facing changes from maintainer-only work.
  6. Call out release blockers, risky changes, missing tests, migration needs, and follow-up issues.

Versioning Guidance

  • Recommend patch for bug fixes and internal hardening.
  • Recommend minor for new features, new public APIs, and compatible behavior additions.
  • Recommend major for breaking API changes, removed behavior, migration requirements, or incompatible config changes.
  • Mark the recommendation as uncertain when the public contract is not clear from the repository.

Output Rules

  • Keep release notes crisp and user-facing.
  • Do not list every commit unless the user asks for a raw changelog.
  • Mention uncertainty and verification gaps explicitly.
  • Include commands run and ranges inspected when the user needs auditability.

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