agentleFS
Sign inStart free
EveryIncEveryInc/hands-on-deck/CLAUDE.md

hands-on-deck

CLAUDE.md209 starsChanged 5 months agoMITView on GitHub

Any change to the skill — skills/hands-on-deck/SKILL.md, deck.py, the docs it ships, or its behavior — must bump the version in the same PR. Two files carry it and they move together: (Leave marketplace.json's top-level metadata.version alone — that's the marketplace's own version, not the plugin's.) Follow semver and the existing commit convention: Commit message format: hands-on-deck X.Y.Z: <one-line summary of the change>.

We split this CLAUDE.md 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. Distinctive:

    Follow semver and the existing commit convention:

    line 12
  2. Very specific:

    Commit message format: hands-on-deck X.Y.Z: <one-line summary of the change>.

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 25,680 CLAUDE.md 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
CLAUDE.md

Working in this repo

Bump the version on every change to the skill

Any change to the skill — skills/hands-on-deck/SKILL.md, deck.py, the docs it ships, or its behavior — must bump the version in the same PR. Two files carry it and they move together:

  • .claude-plugin/plugin.json → version
  • .claude-plugin/marketplace.json → plugins[0].version

(Leave marketplace.json's top-level metadata.version alone — that's the marketplace's own version, not the plugin's.)

Follow semver and the existing commit convention:

  • Patch (3.0.1 → 3.0.2) — guidance tweaks, small fixes, doc changes.
  • Minor (3.0.0 → 3.1.0) — new capabilities or commands.
  • Major — breaking changes to the CLI or patch format.

Commit message format: hands-on-deck X.Y.Z: <one-line summary of the change>.

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