uber-go/zap
GitHubBlazing fast, structured, leveled logging in Go.
- golang
- logging
- structured-logging
- zap
- Stars:
- 24.7k
- Language:
- Go
- Default branch:
- master
- Last scored:
At a glance
- Rank
- #170 of 401
- Top 42% · #25 of 40 Go repos
- Checks passed
- 8 of 17
- Full list below
- Best set up for
- Claude Code
- Score 74.1
- Needs most work for
- Cursor
- Biggest fix: Cursor rules (.cursor/rules) (+11.5 pts)
What it has
What it's missing
What to fix first
Showing fixes for Claude Code
- 1AGENTS.md / CLAUDE.mdAdd an AGENTS.md covering project goals, layout, setup commands, and conventions. Aim for 800+ chars of real guidance (not boilerplate).+13.2 pts
- 2Pre-commit / git hooksSet up pre-commit (.pre-commit-config.yaml), husky, or lefthook to run format+lint on every commit.+5.3 pts
- 3Test suiteAdd a tests/ (or test/, __tests__/, spec/) directory with runnable tests. Document how to run them in AGENTS.md.+3.9 pts
Score for each AI agent
Each agent weighs the checks by its own docs. Under each score are its top three. How each agent is scored →
Does uber-go/zap have agent instructions?
An AGENTS.md (or CLAUDE.md) at the root tells AI coding agents how to build, test and work in the repo. A few agents also read a file of their own.
- AGENTS.md / CLAUDE.md
- None at the root (no AGENTS.md, CLAUDE.md, AGENT.md, .claude/CLAUDE.md or .claude/AGENTS.md)
- Agent-specific files
- None: no GEMINI.md, .cursor/rules, .openhands/setup.sh, .aider.conf.yml or .agents/skills
- Repos that have one
- 23 of 40 Go repos · 221 of 401 repos on the leaderboard · See examples →
Get a starter AGENTS.md
From the files the checks found. Fill in the commands, then commit it at the root.
# AGENTS.md
Guidance for AI coding agents working in uber-go/zap. Blazing fast, structured, leveled logging in Go. Written mainly in Go.
## Where things are
- Dependencies are declared in `go.mod`.
- Test files are spread through the tree, e.g. `array_test.go`.
- Lint and format rules are configured in `.golangci.yml`.
- CI is defined in `.github/workflows`; read it for the exact install, lint and test steps.
- Common tasks are targets in `Makefile`.
- Follow the conventions in `CONTRIBUTING.md`.
## Commands
<!-- Fill in the exact commands CI runs. -->
- Install: TODO
- Test: TODO
- Lint: TODO
All 17 checks · 8 passed
How uber-go/zap compares
- vs leaderboard average
- 3.6 pts above
- Average 66.8
- vs Go average
- 0.6 pts below
- Average 71.0
- Stars among Go repos
- #28 of 40
Missing here, and how many repos have it
- Pre-commit / git hooks · passed by 29% of leaderboard repos, 13% of Go repos
- Skills (.agents/skills) · passed by 17% of leaderboard repos, 10% of Go repos
- Cursor rules (.cursor/rules) · passed by 4% of leaderboard repos, 0% of Go repos
Passes checks most repos miss
- Manageable size · only 16% of repos pass it
One fix for the most agents: AGENTS.md / CLAUDE.md would raise the score for all 9 agents, by up to 13.3 points.
Similar repos
Same language and host as this repo, closest in overall score.
- minio/minio71.8Go · 61.3k ★
- junegunn/fzf71.4Go · 84k ★
- privy-io/go-sdk71.2Go · 4 ★
- gin-gonic/gin70.4Go · 89.5k ★
- spf13/cobra70.4Go · 44.7k ★
- gohugoio/hugo68.2Go · 90.4k ★
Add a badge to your README
Paste this at the top of the README. It shows the score, and links back to this page.
[](https://agentfriendlycode.com/repo/github/uber-go/zap)Check the score on every pull request
A GitHub Action posts one comment per pull request with how the score changed and why.