Checking Code Quality

It's meant for post-refactor validation and catching code smells before they spread, not for blocking emergency fixes. The thresholds are guidelines, not verdicts. You're expected to judge whether a cyclomatic complexity of 15 is genuinely bad or just an honest state machine. If abyss is available, it layers on hotspot analysis to prioritize which files actually matter. The documentation is refreshingly blunt about when to ignore the rules, like exempting CLI entry points from file length limits or accepting magic numbers when they're obviously 0, 1, or 2. Outputs to stdout or JSON for CI pipelines.