nftechie / stonkfly
Code health
Explore this codebase
- Code health map41files scored
- Ownership28sole-owned files: one author, no second reader
- Architecture2modules, 2 entry points
- DecisionsNo decisions recorded yet
- Refactoring7open opportunities, one per file
- TestsNo coverage report yet. Run your tests with coverage on, then add the report:
AlsoDocsChatFilesKnowledge graphChange couplingCommitsStatsCosts
Do next · 3
3 things worth doing in the week to Sep 10, the last indexed commit, 1 of them now.
Now
- High
Start breaking up main (CCN 46, 279 lines): first lift lines 284-304
stonkfly/cli.py:284
main nests deeply; easier to read and change once split; its file is imported by 1 file, changed 1 time in 90 days.
- gain
- +0.8 health on this file(inferred)
- health recoverable
- +0.8(inferred)
- size
- CCN 46, 279 lines, nests 5 deep
- steps
- 1 (1 mechanical)
Small effort
Worth planning
Tidy the code shape this week's commits left: 13 findings in 8 files
1 commit in the last 7 days added or worsened long, complex or deeply nested code, still open. Start with
stonkfly/cli.py(3 findings): tidying it while the change is fresh costs less than after the next one.- code-shape findings
- 13
- files
- 8
- commits
- 1
Medium effortAddress the finding in memory_advance
stonkfly/neural/kernel.cpp:10
memory_advance has a bumpy road finding; changed 1 time in 90 days.
- gain
- up to +0.1 health on this file(inferred)
- finding
- Bumpy road
- size
- CCN 36, 71 lines, nests 6 deep
- severity
- low
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
3 areas
Every detector's open count by area. The actions above are the part worth doing.