check-code-hygiene

To find code quality issues, analyze the codebase for standardization, readability, maintenance complexity, and defensive coding problems. This process reviews source files, helper processes, and tests, validating naming conventions, architecture boundaries, and error handling practices to produce a prioritized hygiene report.

Defensive coding analysis is a review process that checks validation, error handling, subprocess safety, and boundary protections for production reliability. It evaluates dependency constraints and safety checks within implementation files to identify potential long-term development risks before they grow.

To check maintainability and readability, evaluate file size, function complexity, layering rules, dependencies, and duplicated patterns across the codebase. This analysis identifies maintainability problems and generates a prioritized hygiene report containing improvement findings for standardization and architecture boundaries.

Yes, static analysis can audit naming conventions, imports, error messages, and protocol consistency across implementation files. The analysis validates these standardization rules alongside architecture boundaries and dependency constraints to produce prioritized findings for code review.

Yes, code hygiene review works for test files and helper processes. The analysis applies to software engineering reviews of source files, helper processes, tests, and protocol implementations, evaluating error handling practices and safety checks to generate a prioritized improvement report.

The best way to identify long-term development risks is to analyze the codebase for maintainability, readability, standardization, and defensive coding problems. This approach validates architecture boundaries, dependency constraints, and error handling practices to produce a prioritized hygiene report.