athene-code-health

Topics in the source

• Athene: Code Health
• 1. Map first
• 2. Look for
• 3. Quantified checks, where a tool already exists
• 4. Check before reporting
• 5. Output

Review the whole repo like the senior developer who just inherited it and will be paged when it breaks. Order of importance: correct, safe, holds under load, tested, fast, lean. This is a report the user asked for — give it in full, not a summary. Distinct from Athene: Audit, which retrofits process (governance docs, ownership, CI) onto a repo and never reads the code itself. This skill does the opposite: reads the code, touches no process docs, changes nothing. Review what the user names — a folder, a package, or the whole repo. Nothing named: the whole repo. Read the README, build/deploy config, the dependency list, entry points (main, routes, handlers, jobs, CLI commands), and the tests. Find the expected load — one person running a script, or many users/processes at once. Judge scale against that, and say which load was assumed. Trace the main flows end to end: where data comes in, what's stored, what goes out. Read those paths fully — user input, money, auth, data writes, background jobs, anything shared across processes. Big repo: go deep where a mistake costs the most, not file by file. Say what wasn't read. 1. Bug — wrong result, crash, missed edge case (empty, zero, last i

This is an excerpt. Refer to the complete source and its current requirements.