Report · marked 25 Aug 2026
halfrost/LeetCode-Go
An agent will struggle here, mostly for fixable reasons.
Go · 33,792 stars · 6,381 files · branch master
52
/100
C+
Instructions
0/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on agent instruction file and instruction quality.Setup
8/14Whether an agent can install the project and get it running without a human. Losing marks on discoverable commands.Verification loop
19/22Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Losing marks on lint and format rules.Context economy
13/20Whether the repo fits in a context window, or fights it. Losing marks on .gitignore hygiene and file sizes fit in context.Navigability
8/10How quickly anything new can orient itself. Losing marks on written documentation.
Higher is better. Accent marks what is costing you most.
Fix these first
01
Agent instruction file
Add an AGENTS.md at the root: what the project is, how to install, how to run, how to test, and the two or three conventions a newcomer always gets wrong.
02
Instruction quality
Instructions earn their keep by naming exact commands. 'Run the tests with `pnpm test`' beats three paragraphs of philosophy.
03
Discoverable commands
Declare the handful of commands that matter in package.json scripts, a Makefile, or a justfile. Naming them turns guesswork into a lookup.
The full marking
Every deduction below names the file or setting it came from.
Instructions 0/27 F
Whether the repo tells an agent how to behave before it starts guessing.
✗Agent instruction file
0/12
None found. Every agent that opens this repo starts from zero.
Add an AGENTS.md at the root: what the project is, how to install, how to run, how to test, and the two or three conventions a newcomer always gets wrong.
Looked for AGENTS.md, CLAUDE.md, .github/copilot-instructions.md, .cursorrules
✗Instruction quality
0/12
Nothing to judge, since there are no instructions.
Instructions earn their keep by naming exact commands. 'Run the tests with `pnpm test`' beats three paragraphs of philosophy.
✗README as an entry point
0/3
No README. This is the first file anything reads, human or machine.
Give the README an Install and a Usage heading with real commands under each. Agents pattern-match on those headings.
Setup 8/14 B-
Whether an agent can install the project and get it running without a human.
✓Deterministic install
6/6
go.sum pins the dependency tree.
Found go.sum
✗Discoverable commands
0/6
No declared commands. An agent has to infer how to build and run this from the file tree.
Declare the handful of commands that matter in package.json scripts, a Makefile, or a justfile. Naming them turns guesswork into a lookup.
–Environment config
n/a
Not applicable — this reads as a library, with no environment to configure.
✓Pinned runtime version
2/2
The language runtime version is pinned.
go.mod declares a Go version
–Reproducible environment
n/a
Not applicable — a library doesn't need a container to be worked on.
Verification loop 19/22 A
Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy.
✓Tests exist
8/8
810 test files against 1700 source files.
e.g. leetcode/0001.Two-Sum/1. Two Sum_test.go, leetcode/0002.Add-Two-Numbers/2. Add Two Numbers_test.go, leetcode/0003.Longest-Substring-Without-Repeating-Characters/3. Longest Substring Without Repeating Characters_test.go
✓Test command is discoverable
7/7
An agent can find and run `go test ./...`.
✓Continuous integration
4/4
2 GitHub Actions workflows define what "passing" means.
✗Lint and format rules
0/3
No linter or formatter config. Style is tribal knowledge, so agent output will drift from yours.
A formatter config is the cheapest way to stop reviewing whitespace in agent diffs. It moves style from opinion to a command.
–Static type checking
n/a
Not applicable — the Go compiler type checks every build.
Context economy 13/20 B
Whether the repo fits in a context window, or fights it.
✓No committed build output
6/6
No generated directories committed.
✗.gitignore hygiene
2/3
.gitignore has only 3 rules.
Start from a standard template for your stack. It prevents the previous problem before it happens.
✗File sizes fit in context
0/6
5 source files are over 100KB.
A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.
website/public/en.search-data.min.e6589f2e5ab7da3b9eb0bee1547f56f85b01d9cfe3db227ce6aee35ac05e6560.js — 2668KB
website/public/zh.search-data.min.d0d77a4747e93068c8c632be0c1fa853ed2a34004d47429e57c0f958f9aa99c9.js — 2505KB
website/public/prism.js — 104KB
✓Repository weight
5/5
About 43.0MB checked out, which is comfortable.
Here is your AGENTS.md
Drafted from what is actually in this repository: the install
command from your lockfile, the commands you already declare, your real directory layout. Anything
marked TODO needs a person. Save it at the root as AGENTS.md.
# AGENTS.md ✅ Solutions to LeetCode by Go, 100% test coverage, runtime beats 100% | LeetCode 题解 ## Setup ``` go mod download ``` ## Commands ``` go test ./... # run the test suite ``` ## Layout - `leetcode/` 1596 source files - `website/` 57 source files - `ctl/` 18 source files - `structures/` 18 source files - `template/` 10 source files ## Conventions - Tests live alongside the code they cover, following `leetcode/0001.Two-Sum/1. Two Sum_test.go`. - CI defines what passing means. See `.github/workflows/deploy.yml`, and keep it green. - TODO: add the two or three conventions a newcomer always gets wrong here. ## Gotchas - `website/public/en.search-data.min.e6589f2e5ab7da3b9eb0bee1547f56f85b01d9cfe3db227ce6aee35ac05e6560.js` is 2668KB. It will not fit comfortably in context, so read it in parts. --- Drafted by agentreadme.com from what is in this repository. Everything marked TODO needs a human. Check it in as AGENTS.md at the root.
Open the raw markdown
or
curl -o AGENTS.md agentreadme.com/draft/halfrost/LeetCode-Go.md
Show the mark
The badge re-checks daily, so it keeps up as the repository changes. Use mark again to force it now.
[](https://agentreadme.com/halfrost/LeetCode-Go)Other Go repositories, marked
Think this mark is wrong?
Every deduction above names the file it came from, so this can be settled by looking. If a check missed something, that is a rule worth fixing.