BluetOpen source

What agents should know before contributing

rust-lang/rust-analyzer

A Rust compiler front-end for IDEs

Read by Bluet from 3 files written for agents and 300 merged pull requests on 2026-09-25. Not reviewed by the maintainers.

Rules its files tell agents (5)

  • mustFor impossible conditions from which the server can recover, prefer stdx::never!

    Assert invariants liberally. For impossible conditions from which the server can recover, prefer stdx::never! or stdx::always! and return a safe fallback instead of panicking.

    CLAUDE.md
  • shouldDo not author code for issues labeled both E-easy and E-has-instructions.
    CLAUDE.md
  • shouldReuse existing dependencies or stdx; do not add small helper crates without strong justification.

    Be conservative with crates.io dependencies. Reuse existing dependencies or stdx; do not add small helper crates without strong justification.

    CLAUDE.md
  • shouldDo not use AI to author issue/PR comments or replies to maintainers.
    CLAUDE.md
  • shouldDo not autonomously open issues or pull requests.
    CLAUDE.md

Decisions its pull requests settled (3)

  • #23054Parse inline asm with keyword as operand name
  • #22937Report a config error for postfix snippets with item scope
  • #23370restore the server binary check broken by #18281
Your agents can be told this before they touch the code. Get it for your repository: npx bluet-mcp init. What Bluet is.
rust-lang/rust-analyzer: what agents should know before contributing · Bluet