Auditing Naming & Pattern Consistency Across the Repo Workflow Prompt

Overview: Find drift, duplicate utilities, and inconsistent conventions.

SOP Instructions

33 - AUDITING NAMING & PATTERN CONSISTENCY ACROSS THE REPO

Audit this entire repository for naming and pattern drift. Do not change anything yet.

Look for:

1) multiple naming conventions for the same concept:
   - `getUser` vs `fetch_user` vs `userRepository.find()`,
   - `userId` vs `user_id` vs `uid`,
2) different folder or file organizations for the same kind of module,
3) inconsistent error handling patterns,
4) different approaches to validation,
5) different patterns for async/await vs promises vs callbacks,
6) repeated similar utilities that could be consolidated,
7) inconsistent component structure or styling patterns in the frontend,
8) dead code that is no longer used,
9) configuration drift across environments or services,
10) patterns that violate the architecture identified elsewhere.

For each issue, provide:

- the file paths or modules affected,
- what the inconsistency is,
- which pattern is dominant and should be followed,
- why the inconsistency is a problem,
- a low-risk fix.

End with:

- the top ten consistency issues,
- any systemic changes that would prevent future drift,
- a recommendation for which changes are safe to automate vs which need manual review.

Do not make any changes. Provide the audit as a report only.