agentleFS
Sign inStart free
otsalomaotsaloma/agent-setup/skills/review-release/SKILL.md

review-release

Skill0 starsChanged 45 days agoMITView on GitHub

Review changes since the previous release for release

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. testcontainers/testcontainers-node★ 2.6ksame 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 repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Look at git log, changes made since the previous release, i.e.

    line 14
  2. Distinctive:

    Start your report with a verdict: "ready", "ready after fixes" or "not ready".

    line 23

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

Base: $ARGUMENTS — if that's empty, the latest version tag

Look at git log, changes made since the previous release, i.e. the previous version tag. If there's a NEWS.md file, that should also correspond with a release marked as "pending" there, after the previous dated release. Are we now ready to make a release? Are all new features and fixes implemented correctly and coherently? Is there anything left to test or amend? Only review the condition of the codebase. Do not nag about any release mechanics like NEWS.md entries, updating translations, git-tagging or generating release files.

Start your report with a verdict: "ready", "ready after fixes" or "not ready". Then list your findings lettered A, B, etc., ordered by severity "blocker", "should fix" or "minor".

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