code-checker

To find oversized C++ files and functions, you can scan your codebase using configurable effective-line thresholds. This flags translation units, headers, and functions that exceed size limits, generating a markdown report of maintainability hotspots.

Detecting circular dependencies involves parsing GN build metadata and local header includes to map the dependency graph. This process identifies dependency cycles between directory-based modules and outputs a markdown report for troubleshooting.

Running code size analysis without GN build files limits functionality. The circular dependency detection specifically parses GN build metadata to map includes, so projects without GN files will only support standalone size threshold checks for oversized files and functions.

To identify refactoring targets in a large C/C++ codebase, scan for oversized files and functions exceeding effective line count thresholds. This highlights maintainability risks and candidates for decomposition before you begin restructuring.

Circular dependency detection does not work with system or external includes. It specifically analyzes local header includes combined with GN build metadata to identify dependency cycles strictly between internal directory-based modules.