Find Complexity Hotspots with the Code Quality and File Hotspots Scanners

The Vibgrate Code Quality Scanner runs fast AST-based checks for cyclomatic complexity and upgrade-friction hotspots, while the File Hotspots Scanner adds lightweight complexity analysis using filesystem metadata. Together they point at the files most likely to slow down upgrades and refactors.

Prerequisites

• A source-code repository
• Vibgrate CLI installed, or use the no-install form

Steps

1. Install the CLI

npm i -g @vibgrate/cli

Or try it without installing:

npx @vibgrate/cli scan

2. Run the scan

From the repository root:

vg

The Code Quality and File Hotspots scanners run as part of the scan and contribute complexity findings.

3. Review complexity hotspots

The Code Quality Scanner surfaces functions and files with high cyclomatic complexity and upgrade friction. These are prime candidates for refactoring before a major upgrade.

4. Review file hotspots

The File Hotspots Scanner adds a lightweight, filesystem-metadata view of where complexity concentrates, helping you prioritize without a deep parse.

5. Export for refactoring

Emit machine-readable output for planning:

vg scan --format json --out vibgrate.json

Generate a shareable Markdown report:

vg scan --format markdown --out vibgrate.md

Verification

Confirm the scan reported code-quality and file-hotspot findings and that your exported file exists. Cross-check a flagged file in your editor to confirm it is genuinely complex.

Next Steps

Use Vibgrate Graph commands like vg impact to see the blast radius before refactoring a hotspot, and vg tests to find the tests that cover it.