agentleFS
Sign inStart free
sammcjsammcj/agentic-coding/Skills/openspec-bootstrap/CLAUDE.md

agentic-coding / openspec-bootstrap

CLAUDE.md167 starsChanged 10 days agoApache-2.0View on GitHub

After a change that alters how this skill behaves (SKILL.md, assets/config.yaml) - new capability, breaking change, removal, real fix - you MUST add a bullet to CHANGELOG.md under today's date heading (## YYYY-MM-DD, newest first), creating the heading if absent.

We split this CLAUDE.md into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are 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.

  • 2

    Very specific

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

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

    After a change that alters how this skill behaves (SKILL.md, assets/config.yaml) - new capability, breaking change, removal, real fix - you …

    line 5
  2. Distinctive:

    Write more than one line only if a future agent couldn't recover the reasoning from the source.

    line 10
  3. Very specific:

    When you add a changelog entry, set metadata.version in SKILL.md to the same date.

    line 12

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

openspec-bootstrap Rules

Update CHANGELOG.md after changes

After a change that alters how this skill behaves (SKILL.md, assets/config.yaml) - new capability, breaking change, removal, real fix - you MUST add a bullet to CHANGELOG.md under today's date heading (## YYYY-MM-DD, newest first), creating the heading if absent.

  • One line, under 15 words. What changed, not how it was built.
  • Skip trivia: wording, formatting, typos, file moves, no-behaviour refactors. Git history covers those.
  • Squash changes within the same day (do not add changes to changes).
  • Write more than one line only if a future agent couldn't recover the reasoning from the source.
  • No version numbers.
  • When you add a changelog entry, set metadata.version in SKILL.md to the same date.

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