line-checklisted

# line-check A chef's line check before service: walk every station, score it, and leave with an ordered list of what to fix first. The output is not a wall of findings, it is a backlog sorted by leverage (impact relative to effort) that someone could start executing immediately. **Read-only.** Never modify the repo during an audit. If the user wants fixes applied afterward, that is a separate step on a branch. ## Stations Walk all seven. Score each 0-5 (5 = exemplary, 3 = functional with real gaps, 1 = broken or absent, 0 = actively harmful). | # | Station | What to check | |---|---------|---------------| | 1 | Docs and onboarding | README answers what/why/how-fast; quickstart commands actually exist and match the code; examples are current | | 2 | Agent-readiness | AGENTS.md or CLAUDE.md present and accurate; memory/handoff wiring if the project uses it (`.brigade/`, `.claude/memory-handoffs/`); build/test commands documented for agents | | 3 | Tests and CI | Critical paths covered, not just happy paths; CI exists and is green; lint/format gates wired | | 4 | Hygiene | .gitignore excludes agent dirs (`.claude/`, `.codex/`) and build artifacts; LICENSE present (critical if public); no secrets or credentials in the tree; stale branches | | 5 | Structure | Oversized files and god modules; dead code; tangled responsibilities; dependency health (outdated, vulnerable, unused) | | 6 | Release hygiene | CHANGELOG maintained; version in code matches latest tag; tags not far beh