agentleFS
hyodotdevhyodotdev/openiap/.claude/skills/ship-release/SKILL.md

ship-release

Skill166 starsChanged 5 months agoMITView on GitHub

Merge a verified OpenIAP PR, release affected stable packages sequentially with public verification, verify the release note the PR carried, stabilize any correction with review-self, and deploy production docs when the user explicitly requests the full shipping workflow.

12 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 1

    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:

    Read that file first and follow it fully.

    line 9
  2. Very specific:

    Use Claude Code's matching .claude/skills and .claude/commands adapters for the referenced workflows.

    line 13

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

Ship an OpenIAP Release (Claude Code)

The canonical instructions live in .codex/skills/ship-release/SKILL.md. Read that file first and follow it fully. It routes merge, stable package publication, registry verification, release notes, self-review, commits, and production docs deployment through their existing repository SSOT workflows.

Use Claude Code's matching .claude/skills and .claude/commands adapters for the referenced workflows. Preserve the same explicit-authority, sequential release, public-verification, two-clean-snapshot, and direct-main guardrails.

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.