codebase-scout

To analyze an existing Unity project structure for refactor planning, run a directory and file discovery scan to map modules, dependencies, and architecture, generating a concise overview with actionable next steps.

Identifying the tech stack and third-party packages in a Unity codebase involves scanning the directory structure to detect Unity components and packages, outputting a summarized overview to guide design decisions.

Yes, you can assess test coverage and audit module boundaries in a Unity project automatically by running a codebase analysis that evaluates existing tests and maps module dependencies to reveal architectural boundaries.

To generate an onboarding overview for new developers joining a Unity project, scan the project root to map the directory structure, detect components, and output a summarized project state with recommended next steps.

Yes, codebase-scout requires no external dependencies to perform Unity architecture spotting, directly analyzing the project files and directory structure to identify the tech stack and module boundaries.

Automated codebase analysis for Unity feature expansion is limited to mapping directory structure, detecting components, assessing test coverage, and generating summaries, requiring human interpretation for final design decisions.