ln-620-codebase-auditor

Automating a codebase audit involves orchestrating parallel analysis across security, build issues, and code quality. This Skill coordinates nine specialized audit workers to scan for dependency risks, dead code, and concurrency problems, generating a consolidated report in docs/project/codebase_audit.md.

Yes, detecting security vulnerabilities and dependency risks before a release is possible by running a comprehensive codebase assessment. The Skill delegates parallel audits to identify these issues alongside observability gaps and lifecycle management problems, aggregating results into a single report.

The best way to analyze a codebase for code smells and architectural weaknesses is using domain-aware scanning that researches current best practices for your specific tech stack. This Skill detects project domains to apply targeted audits, aggregating findings into a consolidated markdown report.

The codebase audit process works without external dependencies, relying on its internal scripts, references, and assets components. It requires no prerequisite packages to execute its coordinated parallel audit workers and generate the final quality assessment report.

A codebase assessment identifies security vulnerabilities, build issues, code quality concerns, dependency risks, dead code, observability gaps, concurrency problems, and lifecycle management issues by deploying specialized audit workers that perform parallel analysis across the project.

You should run a comprehensive codebase quality analysis before major releases to proactively identify and address security vulnerabilities, code smells, and architectural weaknesses. It aggregates parallel audit results into docs/project/codebase_audit.md to guide final improvements.