Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →notque/codebase-analyzer
Statistical rule discovery from Go codebase patterns.
Passed 16 of 19 test cases with the skill, and 3 of 19 without it.
and 20 more in the full report
15 fixed4 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want to measure how frequently our team uses loggers, test frameworks, and modern Go language features across the repository. Which analysis lens corresponds to frequency measurements, and what primary question does it ask?
| Checked | Without skill | With skill |
|---|---|---|
| identifies Consistency as the lens governing usage frequency | Missed | Passed |
| states the Consistency lens question as how often patterns are used | Missed | Passed |
The instructions your model reads when the skill loads.
Statistical rule discovery through measurement of Go codebases. Python scripts count patterns to avoid LLM training bias, then statistics are interpreted to derive confidence-scored rules. The core principle is Measure First, Interpret Second -- what IS in the code is the local standard, not what an LLM thinks "should be" there.
Load on demand when the corresponding signal appears.
| Signal | Reference | Content |
|---|---|---|
| Three-lens methodology | references/three-lenses.md | Consistency, Signature, Idiom lens details |
| Phase banners, error catalog, reconciliation | references/phase-details.md | Phase templates, rule format, error catalog |
| 100-metric catalog | references/metrics-catalog.md | All metrics across 25 categories |
| Worked examples | references/examples.md | Single repo, multi-repo, evolution tracking workflows |
Goal: Validate target and select analyzer variant.
Read and follow the repository's CLAUDE.md before doing anything else -- project instructions override default behaviors.
Step 1: Validate the target
Step 2: Select cartographer variant
| Variant | Script | Metrics | Use When |
|---|---|---|---|
| Omni (recommended) | cartographer_omni.py | 100 across 25 categories | Full codebase profiling |
| Basic | cartographer.py | ~15 categories | Quick pattern overview |
| Ultimate | cartographer_ultimate.py | 6 focused categories | Performance pattern detection |
Step 3: Verify environment
test cases passed, vs 3 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.