graph-quality-assurance

Run this Skill after writing new code to perform an automated code quality audit. It checks your project against Clean Code, SOLID, DRY, and cyclomatic complexity metrics, then generates a quality report to help reduce technical debt.

A cyclomatic complexity check evaluates the number of independent paths through your code. This Skill uses it alongside Clean Code and SOLID principles to identify overly complex modules, helping reduce technical debt.

Yes, you can integrate these code quality checks into your development workflow. The Skill automates audits during development to continuously enforce project conventions and Clean Code principles without manual intervention.

Yes, running a Clean Code audit requires project-specific configuration and dependencies. This setup allows the automated checks to accurately evaluate your codebase against your defined project conventions and complexity metrics.

The best way to reduce technical debt is performing regular automated checks for SOLID, DRY, and complexity violations. This Skill audits your codebase to identify issues early and generates reports for remediation.

You should avoid running an automated code quality audit if your project lacks established conventions or the required project-specific configuration. Without these dependencies, the Clean Code and complexity checks cannot generate accurate quality reports.