context-slice
CLAUDE.md2 starsChanged 31 days agoMITView on GitHub
Every bump touches all of these files, in one commit named chore: bump version to X.Y.Z: Before committing, check nothing was missed: The grep must return nothing except unrelated matches (e.g. better-sqlite3 in the lockfile). INDEXVERSION in src/storage/sqlite.ts is a separate number. Bump it only when parser output or the stored symbol shape changes (it invalidates users' cached indexes), and regenerate tests/fixtures/rust-parse-snapshot.json with UPDATERUSTPARSESNAPSHOT=1 npx tsx --test tests/rust-parse-snapshot.test.ts. 1. Bump the version (above) and commit. 2. git tag vX.Y.Z, then…
- Commits and pushes
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
- Very specific: line 5
Every bump touches all of these files, in one commit named chore: bump version to X.Y.Z:
- Distinctive: line 18
Before committing, check nothing was missed:
≈ “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.
Files
CLAUDE.md
Bumping the version
Every bump touches all of these files, in one commit named
chore: bump version to X.Y.Z:
| File | Field |
package.json | version |
package-lock.json | version on line 3 and in packages[""] (line 9) — not the dependency versions below it |
plugin.json | version |
.claude-plugin/plugin.json | version |
.claude-plugin/marketplace.json | the plugin entry's version |
tests/package-metadata.test.ts | hardcoded expected version in the packageJson.version assertion |
CHANGELOG.md | new ## X.Y.Z section at the top |
Before committing, check nothing was missed:
git grep -n '<previous version>' -- . ':!CHANGELOG.md' ':!benchmarks' ':!docs'
npm testThe grep must return nothing except unrelated matches (e.g. better-sqlite3
in the lockfile).
INDEX_VERSION in src/storage/sqlite.ts is a separate number. Bump it only
when parser output or the stored symbol shape changes (it invalidates users'
cached indexes), and regenerate tests/fixtures/rust-parse-snapshot.json with
UPDATE_RUST_PARSE_SNAPSHOT=1 npx tsx --test tests/rust-parse-snapshot.test.ts.
Releasing
- Bump the version (above) and commit.
git tag vX.Y.Z, then pushmainand the tag.gh release create vX.Y.Z --title "ContextSlice X.Y.Z" --latestwith the CHANGELOG section as the notes. A tag alone does not create a GitHub release.- The plugin runs the latest published npm
context-slice, so fixes only reach users afternpm publish.
Commits
Short messages. No Co-Authored-By trailer.
In this repository2 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- context-sliceSkill
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
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.