quality-scan

You can detect coding standard deviations and unused imports by running a repository-level quality scan that identifies drift and surfaces both auto-fixable issues and manual items requiring developer attention.

Yes, you can auto-fix code quality issues like formatting and unused imports by running a quality scan that applies trivial fixes automatically and lists manual issues like missing type hints for human action.

Code quality drift is the unnoticed deviation from coding standards, accumulation of unused imports, and hand-rolled helpers. Background scans prevent drift by running automated checks during builds or after epics to surface issues for review.

You should run a code quality scan after completing an epic, before submitting a build, or on-demand to ensure consistent code quality, catch standard deviations early, and reduce review cycles.

No, the quality scan does not auto-fix TODOs or missing type hints. It applies auto-fixes only for trivial issues like formatting and unused imports, while listing manual items for developer action.

The best way to surface hand-rolled helpers and custom drift is to invoke a shell-based quality-scan hook that analyzes source repositories and produces a human-readable findings summary of both auto-fixable and manual issues.