Repo Elegance Review

Overview

Evaluate a codebase for elegance by scanning structure, naming, boundaries, and repo hygiene, then deliver a concise verdict with evidence and prioritized improvements.

Workflow

1) Calibrate

• Ask 1-2 quick questions if “pretty/elegant” is undefined: what they value (structure vs. velocity vs. readability), scope (whole repo vs. area), and constraints (stage/team size).
• Proceed with the default rubric if the user does not respond.

2) Quick Scan (lightweight)

• Map the top-level layout with ls, rg --files, and find . -maxdepth 2 -type d.
• Read README.md, primary config (package.json, pyproject.toml, etc.), and .gitignore.
• Sample a few key directories; avoid full-depth reads unless asked.
• If it is a git repo, check git status -s for untracked noise.