Repo Organization Audit

Run a read-only audit of repository structure, naming hygiene, reuse health, and long-term maintainability. Produce a prioritized report of organization problems with evidence and practical fix direction. Default posture: do not edit, move, rename, reformat, stage, or delete files unless the user explicitly asks for cleanup after the audit.

Core Rules

• Stay read-only during the audit. If the user asks for fixes too, audit first, then switch to normal implementation only after the target changes are clear.
• Focus on organization, discoverability, naming, boundaries, dead code, duplication, reuse opportunities, and long-term maintainability. Do not report ordinary implementation bugs unless they are caused by structural confusion or repeated code.
• Infer conventions from the repo before judging. Existing patterns, framework defaults, monorepo layout, package boundaries, and local naming style matter more than generic preferences.
• Separate confirmed structure problems from subjective preferences. Label judgment calls clearly.
• Prefer actionable findings over broad advice. Every finding should point to concrete files, folders, names, imports, scripts, repeated code, or duplicated concepts.
• Avoid aesthetic nitpicks. A name or folder is a problem only when it creates ambiguity, inconsistency, duplication, poor discoverability, or maintenance risk.
• Respect generated, vendored, build output, migration, lockfile, and third-party directories unless the issue is that they are incorrectly committed or mixed with source.

Inputs

Accept any organization target, including: