agentleFS
Sign inStart free
FuelLabsFuelLabs/fuel-core/AGENTS.md

fuel-core

AGENTS.md57k starsChanged 21 months agoApache-2.0View on GitHub

Guidance for AI coding agents working in this repository (FuelLabs/fuel-core). Before claiming done, committing, or pushing a PR that touches Rust sources, agents must: Keep RUSTVERSIONFMT in sync with .github/workflows/ci.yml (env.RUSTVERSIONFMT, currently nightly-2025-09-28). See CONTEXT.md for Ready vs Health, Height Gap, and Max Sync Height Diff.

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
  1. Distinctive:

    Before claiming done, committing, or pushing a PR that touches Rust sources, agents must:

    line 7
  2. Very specific:

    Keep RUST_VERSION_FMT in sync with .github/workflows/ci.yml (env.RUST_VERSION_FMT, currently nightly-2025-09-28).

    line 21
  3. Very specific:

    Never: run cargo fmt / cargo fmt --all on the stable / 1.94.1 toolchain from rust-toolchain.toml.

    line 25
  4. Very specific:

    Prefer formatting the whole workspace with the CI nightly (cargo +nightly-2025-09-28 fmt --all) so the PR matches CI.

    line 26

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

AGENTS.md

Guidance for AI coding agents working in this repository (FuelLabs/fuel-core).

Required quality gate (do not skip)

Before claiming done, committing, or pushing a PR that touches Rust sources, agents must:

  1. Format with the same nightly rustfmt CI uses (not the pin in rust-toolchain.toml).
  2. Confirm the check is clean.
# Install once if missing
rustup toolchain install nightly-2025-09-28 --component rustfmt

# Apply + verify (matches `.github/workflows/ci.yml` `rustfmt` job)
cargo +nightly-2025-09-28 fmt --all
cargo +nightly-2025-09-28 fmt --all -- --check

Keep RUST_VERSION_FMT in sync with .github/workflows/ci.yml (env.RUST_VERSION_FMT, currently nightly-2025-09-28).

Hard rules

  • Never run cargo fmt / cargo fmt --all on the stable / 1.94.1 toolchain from rust-toolchain.toml. .rustfmt.toml uses nightly-only options (imports_layout, imports_granularity, normalize_comments, trailing_semicolon). Stable ignores them and can rewrite hundreds of files with compact import layout.
  • Prefer formatting the whole workspace with the CI nightly (cargo +nightly-2025-09-28 fmt --all) so the PR matches CI. If you must format a subset, still use that nightly + this repo's .rustfmt.toml.
  • Also run cargo clippy (stable pin) with -D warnings on touched crates when practical; CI enforces warnings as errors.

Commands (matrix)

StepCommand
Setupcargo fetch
Buildcargo build
Testcargo test
Format (required)cargo +nightly-2025-09-28 fmt --all then -- --check
Lintcargo clippy -- -D warnings (scoped to changed crates is OK)
Local CI-ishsource ci_checks.sh

Domain / readiness language

See CONTEXT.md for Ready vs Health, Height Gap, and Max Sync Height Diff.

Download now (ZIP)

Trending

Quiet this year.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the FuelLabs/fuel-core repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about FuelLabs/fuel-core

The biggest 5 of 52 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 52

Talked about on GitHub, Bluesky and YouTube (52 times).

On GitHub · 41

36 more on GitHub

On Bluesky · 10

5 more on Bluesky

On YouTube · 1

  • 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 28,693 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.

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