size-check

Static analysis checks enforce code size and complexity limits during refactoring by flagging oversized functions, files, deeply nested constructs, and god classes. This ensures new code adheres to maintainability guidelines.

A god class is a large module handling too many responsibilities. You detect it in your codebase by applying static analysis rules that flag oversized files and modules, signaling refactoring opportunities for better abstraction and Single Responsibility Principle adherence.

Code complexity static analysis works with TypeScript, Python, Go, Rust, and JavaScript. The size thresholds are language-agnostic, meaning no language reference files are needed to count function lines, nesting depth, and parameter counts.

You check function length and parameter counts by running size-check rules on your repository. This identifies bloated functions and excessive parameter lists, promoting better abstraction and improving overall code quality and readability.

The SIZE-1 through SIZE-6 rules in static analysis are code quality constraints that count function lines, file lines, nesting depth, parameter counts, flag arguments, and detect god classes. They prevent oversized constructs across multiple programming languages.

You can use code size rules for code reviews without language-specific configuration because the size thresholds are language-agnostic. The rules apply uniformly across TypeScript, Python, Go, Rust, and JavaScript without needing reference files.