agentleFS
Sign inStart free
IronAdamantIronAdamant/Chisel/CLAUDE.md

Chisel

CLAUDE.md5 starsChanged 7 days agoMITView on GitHub

The product is the Rust crate in src/. Read AGENTS.md for how to call it and ARCHITECTURE.md for the module map. Build with cargo build --release. The chisel binary is src/main.rs. The chisel-mcp binary is src/bin/chisel-mcp.rs. Both call the same entry point. Storage is the snapshot .chisel/store. Chisel does not open chisel.db. :memory: and file: storage paths are rejected. Do not pip-install Chisel. Do not use SQLite as the store. Cargo.toml dependency tables stay empty. There is no build.rs. looks_like_test…

  • In this repository2 other files it gives its agents.

The file

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

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    Do not pip-install Chisel.

    line 7

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 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

Chisel

The product is the Rust crate in src/. Read AGENTS.md for how to call it and ARCHITECTURE.md for the module map.

Build with cargo build --release. The chisel binary is src/main.rs. The chisel-mcp binary is src/bin/chisel-mcp.rs. Both call the same entry point. Storage is the snapshot .chisel/store. Chisel does not open chisel.db. :memory: and file: storage paths are rejected.

Do not pip-install Chisel. Do not use SQLite as the store. Cargo.toml dependency tables stay empty. There is no build.rs.

looks_like_test in src/engine/mod.rs is the only test-file classifier. Rust files under tests/ are tests. #[test] functions are test units.

Status values: no_data, no_changes, no_edges, git_error, stale_db, error, unsupported, auto_queued. no_data and stale_db exit 0. error and git_error exit 1.

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