codebase-inspection

Codebase metrics analysis measures lines of code, file counts, and language distribution using pygount. It breaks down code composition into actual code, comments, and empty lines to help you understand project size and structure.

Run pygount with the folders-to-skip parameter to exclude directories like node_modules, venv, and build from your lines of code analysis. This ensures your LOC metrics reflect only your actual project source files.

Yes, pygount is applicable for code reviews and repository audits by providing a quick summary of project size and code composition. You can assess the percentage of code lines, comments, and empty lines before presenting a project for review.

The best way to get a summary of file types and language distribution is using pygount with the summary format flag. It analyzes your codebase structure and identifies which programming languages are used along with their file counts.

Yes, you need to install pygount as it is a required dependency for executing local codebase measurement. The Skill relies on pygount to analyze codebases for LOC, file types, and language breakdown directly on your machine.

Yes, during a codebase inspection pygount can identify empty and binary files as part of its file count metrics. This allows you to understand exactly what files exist in your repository beyond just standard source code.