investigate-directory

To audit a directory, analyze its content, structure, and project context to infer the true purpose and assess quality signals like naming consistency. This generates a plain-language assessment without modifying any files.

Directory structure analysis reveals what a folder actually does beyond its label. It identifies scope, detects convention drift, and recommends actions for code consolidation or reorganization based on actual project content.

Yes, you can apply the audit to target directories within the repository and across projects. It evaluates code quality signals including naming consistency, key file presence, and alignment with project guidelines.

You check folder alignment by inferring purpose from project context and comparing it against established conventions. The audit reports naming consistency, key file presence, and any detected drift from expected standards.

No, the directory audit is strictly read-only and does not modify files or create tasks. It only analyzes the target directory path and generates a practical assessment of its purpose and quality.

The best way to identify scope drift is to audit the directory's content and structure against project context. This produces a practical assessment describing drift and recommending actions for reorganization.