Report · marked 26 Aug 2026
go-gitea/gitea
Solid foundations, held back in a few specific places.
Go · 57,604 stars · 6,244 files · branch main
82
/100
A-
Instructions
22/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on instruction quality and readme as an entry point.Setup
16/20Whether an agent can install the project and get it running without a human. Losing marks on environment config.Verification loop
22/22Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Full marks.Context economy
11/20Whether the repo fits in a context window, or fights it. Losing marks on file sizes fit in context and repository weight.Navigability
10/10How quickly anything new can orient itself. Full marks.
Higher is better. Accent marks what is costing you most.
Fix these first
01
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.
02
Environment config
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.
03
Instruction quality
Worth fixing: has no headings to structure it; has no code blocks.
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
12/12
AGENTS.md is present, which is the format the most tools read.
Also found: CLAUDE.md
✗Instruction quality
8/12
Real instructions, with gaps.
Worth fixing: has no headings to structure it; has no code blocks.
2,412 characters, a workable length
names the actual commands to run
✗README as an entry point
2/3
README exists but never explains how to get the thing running.
Give the README an Install and a Usage heading with real commands under each. Agents pattern-match on those headings.
Setup 16/20 A-
Whether an agent can install the project and get it running without a human.
✓Deterministic install
6/6
pnpm-lock.yaml pins the dependency tree.
Found pnpm-lock.yaml
✓Discoverable commands
6/6
Commands are declared where an agent will look for them.
Makefile
✗Environment config
0/4
Nothing documents the environment this needs. An agent will get a runtime error it can't diagnose.
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.
package.json engines.node >= 22.18.0
✓Reproducible environment
2/2
.devcontainer/devcontainer.json gives a known-good environment.
Verification loop 22/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
2002 test files against 3343 source files.
e.g. build/openapi3gen/convert_test.go, build/openapi3gen/enumscan_test.go, cmd/admin_auth_ldap_test.go
✓Test command is discoverable
7/7
An agent can find and run `go test ./...`.
✓Continuous integration
4/4
17 GitHub Actions workflows define what "passing" means.
✓Lint and format rules
3/3
eslint.config.ts encodes the house style.
–Static type checking
n/a
Not applicable — the Go compiler type checks every build.
Context economy 11/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 84 patterns.
✗File sizes fit in context
0/6
1 source file is 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.
modules/emoji/emoji_data.go — 364KB
✗Repository weight
2/5
About 354MB checked out. Large enough that cloning and searching are both slow.
Large binaries and vendored trees slow every operation an agent performs. Git LFS or a separate assets repo keeps the working tree navigable.
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 Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD ## Setup ``` pnpm install ``` ## Commands ``` make help make clean-all make clean make fmt make fmt-check make generate-swagger ``` ## Layout - `modules/` 1038 source files - `services/` 500 source files - `routers/` 462 source files - `models/` 375 source files - `modelmigration/` 340 source files - `tests/` 289 source files ## Conventions - Tests live alongside the code they cover, following `build/openapi3gen/convert_test.go`. - TypeScript runs in strict mode. Type errors are the fastest feedback available, so do not weaken it. - CI defines what passing means. See `.github/workflows/cache-prune.yml`, and keep it green. - TODO: add the two or three conventions a newcomer always gets wrong here. ## Gotchas - Generated output is committed (`build/`). Search will return the compiled copy, so edit the source, not that. - `modules/emoji/emoji_data.go` is 364KB. 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/go-gitea/gitea.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/go-gitea/gitea)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.