dietrichgebert / ponytail
Code health
Hotspots average 6.8, the place fixes pay off most.
Explore this codebase
- Code health map5hotspots across 156 files
- Ownership18sole-owned files: one author, no second reader
- Architecture7modules, 3 entry points
- Decisions75recorded, of which 0 in force and 75 background
- Refactoring7open opportunities, one per file
- TestsNo coverage report yet. Run your tests with coverage on, then add the report:
AlsoDocsChatFilesKnowledge graphChange couplingCommitsStatsCosts
Do next · 4
4 things worth doing in the week to Oct 29, the last indexed commit.
Worth planning
Break up register (CCN 62, 221 lines)
hooks/band/register.tsx:257
register has many paths; easier to read and change once split, which also removes a duplicate; function changed in 8 commits; changed 10 times in 90 days.
- gain
- up to +3.2 health on this file(inferred)
- finding
- Complex method
- size
- CCN 62, 221 lines
- severity
- high
Medium effort, worth a checkTidy the code shape this week's commits left: 1 finding in
hooks/band/register.tsx1 commit in the last 7 days added or worsened long, complex or deeply nested code, still open. Start with
hooks/band/register.tsx(1 finding): tidying it while the change is fresh costs less than after the next one.- code-shape findings
- 1
- files
- 1
- commits
- 1
Medium effortStart breaking up finish (CCN 66, 119 lines): first lift lines 90-102
hooks/ponytail-mode-tracker.js:90
finish has many paths; easier to read and change once split; function changed in 15 commits; changed 11 times in 90 days.
- gain
- up to +3.6 health on this file(inferred)
- finding
- Complex method
- size
- CCN 66, 119 lines, nests 5 deep
- severity
- high
Medium effort, worth a checkStart breaking up activate (CCN 42, 96 lines): first lift lines 32-71
hooks/ponytail-activate.js:32
activate has many paths; easier to read and change once split; function changed in 6 commits; changed 10 times in 90 days.
- gain
- up to +3.6 health on this file(inferred)
- finding
- Complex method
- size
- CCN 42, 96 lines, nests 4 deep
- severity
- high
Medium effort, worth a check
Improve what Repowise can see
Add a test coverage report
Without one, Repowise cannot tell tested code from untested code, so every test-related action says “unknown”.
- line coverage
- Unknown, no report
Small effort
Everything we found
5 areas
Every detector's open count by area. The actions above are the part worth doing.
- Code health213 open findingsCriticalComplex method · hooks/ponytail-mode-tracker.js16 findings · 8.0 deducted
- Refactoring7 open opportunitiesLowrun+0.4 health, S effort · benchmarks/agentic/complete.py
- Doc drift10Mediumexamples/email-validation.mdDocument names benchmarks/output.json, which no longer exists.
- Decisions0 drifting from the codeMediumtests/hooks.test.jsHigh-churn file with no governing decision
- Ownership18 sole-owned filesMediumhooks/band/metrics.tsOne author, no second reader