agentleFS
Zwin-uxZwin-ux/kit/skills/ship-checklist/SKILL.md

ship-checklist

Skill0 starsChanged 11 days agoMITView on GitHub

Run a practical pre-ship checklist for an app release.

5 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

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check build and typecheck if the project has them.

    line 14
  2. Distinctive:

    Run tests that cover the changed area.

    line 15
  3. Distinctive:

    Verify env and config examples still match real usage.

    line 16
  4. Distinctive:

    Check for secrets, debug flags, and temporary code.

    line 17

“Common” is measured: kept by at least 6 in 10 of the 4 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. Confirm the change set and intended release scope.
  2. Check build and typecheck if the project has them.
  3. Run tests that cover the changed area.
  4. Verify env and config examples still match real usage.
  5. Check for secrets, debug flags, and temporary code.
  6. Confirm README or changelog notes if user-facing behavior changed.
  7. Produce a pass/fail checklist with remaining blockers only.

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.