Code Quality Scan

Process

0. Detect build system and tools. See ./references/tool-guidance.md for the full tool matrix per language.

   • If flake.nix exists: use nix build, nix flake check, nix run .#test, nix run .#lint
   • Else if go.mod exists: use go build ./..., go vet ./..., go test ./...
   • Else: detect from the table in tool-guidance.md

1. Run the build command. If it fails, every build error is a Critical finding.

2. Run the lint command. For Go: golangci-lint run ./... (or go vet ./... as fallback). Map each finding to a severity using the classification in tool-guidance.md.

3. Run the duplicate code finder.

   • Use art-dupl --type-aware --sort total-tokens -t 5 --html for Go
   • If art-dupl is not installed, fall back to jscpd
   • See ./references/tool-guidance.md → Go duplication

4. Collect and classify all findings by severity (Critical / High / Medium / Low).