match-codebase-conventions

To find inconsistencies in coding conventions, scan the repository to map file naming, directory structure, error handling, testing, and documentation usage across multiple files. This surfaces alignment gaps where patterns are codified or implicit.

Comparing your codebase against ADRs and style guides involves scanning for explicit rules in documentation and matching them against actual file and directory patterns. This identifies deviations from established architecture decisions.

Harmonizing project conventions with minimal disruption requires mapping all alignment gaps first, then generating an actionable plan that prioritizes consistent patterns for file naming, structures, and error handling without breaking existing logic.

Yes, you can detect implicit coding conventions by analyzing multiple files for consistent naming, directory structure, and error handling patterns. This surfaces unwritten rules that lack explicit documentation in ADRs or CONTRIBUTING files.

Inconsistent file naming and directory structure occurs when conventions remain implicit and lack explicit rules in ADRs or style guides. Scanning the codebase identifies these alignment gaps between documented principles and actual implementation.