agentleFS
hhopkehhopke/intervals-icu-mcp/.claude/skills/release-check/SKILL.md

release-check

Skill121 starsChanged 9 days agoMITView on GitHub

Run the full pre-release verification suite and summarize results. Use when the user asks to check if the code is ready for release, before any PR/merge, or when finishing a feature.

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use review.

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.
  • SentrySkill

    review

    Fixture review skill.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 3

    Distinctive

    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. Distinctive:

    Run the full pre-release check:

    line 12
  2. Very specific:

    Check the version-bump inputs.

    line 17
  3. Distinctive:

    If tests fail, offer to run the specific failing test in verbose mode:

    line 50
  4. Distinctive:

    If lint fails, offer to auto-fix:

    line 55

“Common” is measured: kept by at least 6 in 10 of the 13 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Instructions

  1. Run the full pre-release check:
    make can-release
  2. Check the version-bump inputs. The conventional-commit type of each merged PR title sets the version bump (release notes are written into a draft at release time by /release-write). CHANGELOG.md is frozen at 5.8.0, so don't check or edit it. PRs are squash-merged, so each main commit subject is a PR title. Preview the next release:

    python3 .github/scripts/next_version.py

    It lists every commit since the last tag with the bump it asks for, warns about non-conventional subjects, and prints the computed version. Report:

    • any non-conventional subject (it counts as a patch);
    • any commit whose type looks wrong for what it did: a user-facing addition or a response-shape change titled fix/chore (should be feat), or a breaking change per CLAUDE.md with no ! (would ship as minor/patch instead of major). Check the PR (gh pr view N, N from the (#N) suffix) when the subject alone is ambiguous.

    Titles can't be changed after merge. Fix a wrong bump by passing -f version=X.Y.Z when dispatching the release. Misleading titles don't matter for the notes: they are rewritten in the draft before publishing.

  3. Parse the output and report a clear summary:

    If everything passes:

    ✅ Release check passed. All tests, linting (ruff + pyright), and formatting checks are green, and every commit since the last tag has a conventional title. Next release: vX.Y.Z (<bump>).

    If something fails:

    ❌ Release check failed.

    List each failing check with:

    • What failed (test name, lint rule, file, or a mistyped or non-conventional commit title)
    • A brief explanation of the issue
    • A suggested fix
  4. If tests fail, offer to run the specific failing test in verbose mode:
    make test/verbose
  5. If lint fails, offer to auto-fix:
    make format

What make can-release checks

  • make lint — ruff check + pyright type checking
  • make test — full pytest suite
  • Code formatting compliance

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.