Codebase Inspection — Inspect codebases w/ pygount: LOC, languages, ratios
Codebase Inspection — Inspect codebases w/ pygount: LOC, languages, ratios
Start with meaning, then move to detail.
This lesson explains Codebase Inspection — Inspect codebases w/ pygount: LOC, languages, ratios as part of extending Hermes and connecting external tools. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Skill metadata, Reference: full SKILL.md, When to Use, then verify failure modes and version compatibility.
Complete installation and one successful task before adding new capabilities.
A clear outcome before you read.
- Understand Codebase Inspection — Inspect codebases w/ pygount: LOC, languages, ratios without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Skill
- An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
Inspect codebases w/ pygount: LOC, languages, ratios
What does the source say, and in what order?
- 01Skill metadata
Start here to understand the core idea or structure.
- 02Reference: full SKILL.md
Read this after the foundation, then connect it to the previous step.
- 03When to Use
Read this after the foundation, then connect it to the previous step.
- 04Prerequisites
Read this after the foundation, then connect it to the previous step.
- 051. Basic Summary (Most Common)
Read this after the foundation, then connect it to the previous step.
- 062. Common Folder Exclusions
Read this after the foundation, then connect it to the previous step.
- 073. Filter by Specific Language
Read this after the foundation, then connect it to the previous step.
- 084. Detailed File-by-File Output
Read this after the foundation, then connect it to the previous step.
- 095. Output Formats
Read this after the foundation, then connect it to the previous step.
- 106. Interpreting Results
Finish here to verify the result and special cases.
Copy only after you understand the effect.
pip install --break-system-packages pygount 2>/dev/null || pip install pygountcd /path/to/repo
pygount --format=summary \
--folders-to-skip=".git,node_modules,venv,.venv,__pycache__,.cache,dist,build,.next,.tox,.eggs,*.egg-info" \
.# Python projects
--folders-to-skip=".git,venv,.venv,__pycache__,.cache,dist,build,.tox,.eggs,.mypy_cache"
# JavaScript/TypeScript projects
--folders-to-skip=".git,node_modules,dist,build,.next,.cache,.turbo,coverage"
# General catch-all
--folders-to-skip=".git,node_modules,venv,.venv,__pycache__,.cache,dist,build,.next,.tox,vendor,third_party"Read the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.