senior-software-analyst

Follow a phased audit: read the README and manifest files, locate the entry point, map the module structure, review dependencies, and trace configuration and data flow. This Skill automates that sequence with concrete grep, find, and build commands.

Run compiler lints such as cargo clippy with dead_code warnings for Rust or ts-prune for TypeScript to surface unused functions and exports. Then flag anti-patterns like god objects, circular dependencies, magic values, and missing error handling.

Use codebase analysis when you need to understand an entire project's architecture and health before changing anything. Use PR-scoped code review when evaluating a specific diff, since review requires change-focused context rather than full system mapping.

Yes, it supports a multi-agent team pattern where separate analysts audit frontend, backend, and infrastructure in parallel. A lead agent then synthesizes the individual results into a unified codebase report.

The audit relies on static inspection via grep and build checks, so it cannot verify runtime behavior or business logic correctness. Security vulnerability assessment is also out of scope and should be delegated to a dedicated security audit process.