// Use when understanding project composition by language, measuring code change impact, or generating code statistics for CI/CD metrics
| name | analyzing-code |
| description | Use when understanding project composition by language, measuring code change impact, or generating code statistics for CI/CD metrics |
Always invoke analyzing-code skill for code statistics - do not execute bash commands directly.
Use tokei for fast, accurate code statistics across multiple languages and projects.
Invoke analyzing-code skill for analyzing code statistics by language. Use when understanding project composition, measuring change impact before refactoring, or generating CI/CD metrics.
Common workflow: analyzing-code skill → other skills (finding-files, querying-json, querying-yaml) for filtering or analyzing-code skill after refactoring to measure impact.
-f/--files show individual file statistics-l/--languages list supported languages and extensions-v/--verbose show unknown file extensions (1-3)-V/--version show version information--hidden include hidden files-c/--columns N set strict column width-t/--type TYPES filter by language types (comma-separated)-e/--exclude PATTERNS exclude files/dirs (gitignore syntax)--no-ignore don't respect ignore files
--no-ignore-dot don't respect .ignore/.tokeignore--no-ignore-vcs don't respect VCS ignore files--no-ignore-parent don't respect parent ignore files-o/--output FORMAT output format (json|yaml|cbor)
cargo install tokei --features all-i/--input FILE read from previous tokei run or stdin-s/--sort COLUMN sort by column
files|lines|blanks|code|commentsFor comprehensive usage patterns, output formats, language filtering, and integration examples, load tokei guide when needing:
The guide includes:
# Get language breakdown and filter for top languages
tokei -o json | jq '.data | to_entries | sort_by(.value.stats.code) | reverse | .[0:5] | .[].key'
# Analyze changes after refactoring
git diff --name-only | xargs tokei --files
# Find and analyze specific components
fd -e py src/components | xargs tokei -t Python
Use when implementing any feature or fix using TDD, before writing any implementation code
Use when domain logic leaks into API/Infrastructure, project references violate layer boundaries, or you need to decide between CQS (always), CQRS bus (complex domains), and DDD patterns (invariants and events).
Use when configuring Git hooks in .NET projects before team commits occur, to enforce commit message standards and code formatting automatically
Use before writing any test or implementation task, when observable behavior needs to be captured in business language scenarios and approved by the user before code begins
Use when running mutation testing, killing mutants, verifying test quality, checking mutation score, or analyzing survivors after the test baseline is green
Use when writing tests from the outside-in, defining behavior before code, or any feature where tests should start from observable business behavior and let internal design emerge