Report · marked 27 Aug 2026

jesseduffield/lazydocker

Solid foundations, held back in a few specific places.

Go · 52,624 stars · 1,547 files · branch master

82 /100 A-

Instructions 22/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on agent instruction file and instruction quality.Setup 18/20Whether an agent can install the project and get it running without a human. Losing marks on environment config.Verification loop 18/22Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Losing marks on tests exist.Context economy 14/20Whether the repo fits in a context window, or fights it. Losing marks on file sizes fit in context.Navigability 9/10How quickly anything new can orient itself. Losing marks on repository description.

Higher is better. Accent marks what is costing you most.

Fix these first

File sizes fit in context

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.

Tests exist

Coverage is thin enough that an agent can break real behavior and still see green.

Agent instruction file

Rename or symlink to AGENTS.md so tools other than one vendor's can read it. Keeping CLAUDE.md alongside it costs nothing.

The full marking

Every deduction below names the file or setting it came from.

Instructions 22/27 A-

Whether the repo tells an agent how to behave before it starts guessing.

✗Agent instruction file 9/12

CLAUDE.md is present, but not the vendor-neutral AGENTS.md.

Rename or symlink to AGENTS.md so tools other than one vendor's can read it. Keeping CLAUDE.md alongside it costs nothing.

✗Instruction quality 10/12

Specific enough that an agent can act on it.

Worth fixing: has no code blocks.

205 characters, a workable length

names the actual commands to run

uses headings, so an agent can skim it

✓README as an entry point 3/3

README has a clear getting-started section.

Setup 18/20 A

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 6/6

Commands are declared where an agent will look for them.

scripts/ directory

✗Environment config 2/4

Env vars are mentioned in the README but there's no example file to copy.

Add a .env.example listing every variable with a safe placeholder value. It's the cheapest possible fix and it unblocks the whole first run.

✓Pinned runtime version 2/2

The language runtime version is pinned.

go.mod declares a Go version

✓Reproducible environment 2/2

.devcontainer/devcontainer.json gives a known-good environment.

Verification loop 18/22 A-

Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy.

✗Tests exist 4/8

13 test files against 1196 source files.

Coverage is thin enough that an agent can break real behavior and still see green.

e.g. pkg/commands/container_stats_test.go, pkg/commands/docker_test.go, pkg/commands/os_test.go

✓Test command is discoverable 7/7

An agent can find and run `go test ./...`.

✓Continuous integration 4/4

3 GitHub Actions workflows define what "passing" means.

✓Lint and format rules 3/3

.golangci.yml encodes the house style.

–Static type checking n/a

Not applicable — the Go compiler type checks every build.

Context economy 14/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 3/3

.gitignore covers 5 patterns.

✗File sizes fit in context 0/6

14 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.

vendor/golang.org/x/sys/windows/zerrors_windows.go — 923KB

vendor/github.com/rivo/uniseg/lineproperties.go — 292KB

vendor/golang.org/x/sys/unix/ztypes_linux.go — 251KB

✓Repository weight 5/5

About 30.2MB 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 — drafted for jesseduffield/lazydocker

# AGENTS.md

The lazier way to manage everything docker

## Setup

```
go mod download
```

## Commands

```
go test ./...   # run the test suite
```

## Layout

- `vendor/`  1102 source files
- `pkg/`     84 source files
- `scripts/` 5 source files
- `test/`    1 source file

## Conventions

- Tests live alongside the code they cover, following `pkg/commands/container_stats_test.go`.
- CI defines what passing means. See `.github/workflows/cd.yml`, and keep it green.
- TODO: add the two or three conventions a newcomer always gets wrong here.

## Gotchas

- `vendor/golang.org/x/sys/windows/zerrors_windows.go` is 923KB. 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/jesseduffield/lazydocker.md

Show the mark

The badge re-checks daily, so it keeps up as the repository changes. Use mark again to force it now.

[![agent ready](https://agentreadme.com/badge/jesseduffield/lazydocker.svg)](https://agentreadme.com/jesseduffield/lazydocker)

Other Go repositories, marked

avelino/awesome-go 78 A- ollama/ollama 88 A golang/go 31 D kubernetes/kubernetes 74 B+ microsoft/TypeScript 82 A- fatedier/frp 96 A+

All Go repositories

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.

Open an issue, already filled in