agentleFS
Sign inStart free
BoshenBoshen/cargo-shear/AGENTS.md

cargo-shear

AGENTS.md583 starsChanged 32 days agoMITView on GitHub

Detect and fix unused dependencies, misplaced dependencies, and unlinked source files in Rust projects. After making code changes, run just ready — it runs typos, fmt, check, lint, and tests, and must pass before work is considered complete.

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repositoryOne other file it gives its agents.

The file

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

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

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    After making code changes, run just ready — it runs typos, fmt, check, lint, and tests, and must pass before work is considered complete.

    line 7
  2. Distinctive:

    Follow existing Rust idioms and patterns in the codebase.

    line 20
  3. Very specific:

    All code must pass the strict lints configured in Cargo.toml.

    line 21
  4. Very specific:

    Prefer ast-grep for syntax-aware searches in Rust source.

    line 22

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

cargo-shear

Detect and fix unused dependencies, misplaced dependencies, and unlinked source files in Rust projects.

Development workflow

After making code changes, run just ready — it runs typos, fmt, check, lint, and tests, and must pass before work is considered complete.

Frequent commands

  • just ready — full quality checks (typos, fmt, check, lint, test)
  • just fmt — format with rustfmt and taplo
  • just lint — clippy
  • just snapshots — accept snapshot test changes
  • cargo test — run all tests
  • cargo check — quick compile check

Code standards

  • Follow existing Rust idioms and patterns in the codebase.
  • All code must pass the strict lints configured in Cargo.toml.
  • Prefer ast-grep for syntax-aware searches in Rust source.

Key modules

  • src/lib.rs — core library entry point
  • src/source_parser.rs — parses Rust source for imports and file paths
  • src/package_analyzer.rs — finds unused dependencies and unlinked files
  • src/package_processor.rs — processes packages (unused, misplaced deps, etc.)
  • src/cargo_toml_editor.rs — edits Cargo.toml
  • src/manifest.rs — manifest parsing and types
  • src/context.rs — workspace and package context types
  • src/diagnostics.rs — diagnostic types and analysis results
  • src/output.rs, src/output/ — output formatting (miette, JSON, GitHub Actions)

Testing

  • Unit tests: src/tests.rs
  • Integration tests: tests/integration_tests.rs
  • Test fixtures: tests/fixtures/
  • Snapshot tests use cargo-insta (just snapshots to accept changes)

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