Loops Housenear-doctor

NEAR HACKATHON
Links
Team
1 member- SVOwner
S Varma
Overview
NEAR developers and their coding agents keep losing time to a small set of repeatable problems that the usual checks miss: a contract whose unit tests pass but whose wasm build fails because a helper shares a name with a #[near] method, scripts that call CLI commands that no longer exist, clients written against near-api-js 0.x APIs that v7 removed, and clippy failures on code the #[near] macro generates. near-doctor is an npm CLI (npx near-doctor, zero dependencies) that scans a NEAR project in under a second and reports each problem with file, line, cause, fix and an evidence tier. It explains pasted error output, applies a small allowlisted set of deterministic fixes (fix --safe), and gives coding agents a task plus an acceptance command for everything else. Its friction log has 18 records, each tagged verified-here, reported or hypothesis, and every rule must fire on a reproduction and stay silent on a control in CI, so an untested rule cannot ship. One widely reported error (PrepareError(Deserialization)) did not reproduce on current testnet, so it is marked historical and never warns. We ran the rules over 150 public hackathon repos by reading source, found false positives in four of our own rules, fixed them, and published only counts in docs/STUDY.md. Contributors report friction through a GitHub issue form; a deterministic workflow matches it to the log or drafts a rule for a maintainer to reproduce. A proof-of-concept harness also hands one finding (F-001) to a coding agent and accepts its patch only if near-doctor and cargo near check agree; one live Codex run passed (transcript in docs/). NEAR fit: it wraps cargo-near and checks near-sdk, near-api-js v7 and near-cli usage, and its evidence comes from reproductions on the NEAR toolchain and testnet. It holds no keys and sends no transactions. Limits: tested on macOS arm64 only; the scanners are lightweight, not compilers.