amibamae / gameserver-controller
gomain354ee6a67.0K linessynced on Nov 14, 2026
Since the previous index, +13 files+0.2 code health+0.3 hotspot health
Code health
6.2out of 10Fair
Hotspots average 3.8, the place fixes pay off most.
Explore this codebase
- Code health map49hotspots across 904 files
- Ownership282sole-owned files: one author, no second reader
- Architecture6modules, 8 entry points
- Decisions8recorded, of which 8 accepted and 0 awaiting review
- Refactoring75open opportunities, one per file
- TestsNo coverage report yet. Run your tests with coverage on, then add the report:
AlsoDocsChatFilesKnowledge graphChange couplingCommitsStatsCosts
Do next · 1
1 thing worth doing in the week to Nov 14, the last indexed commit.
Worth planning
Tidy the code shape this week's commits left: 40 findings in 28 files
22 commits in the last 7 days added or worsened long, complex or deeply nested code, still open. Start with
internal/wasabistorage/operations.go(4 findings): tidying it while the change is fresh costs less than after the next one.- code-shape findings
- 40
- files
- 28
- commits
- 22
Large effort
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
4 areas
Every detector's open count by area. The actions above are the part worth doing.
- Code health1,472 open findingsCriticalChange entropy · internal/workflow/server_backup.go85 findings · 14.4 deducted
- Refactoring75 open opportunitiesLowObserve+0.3 health, S effort · internal/integrationmonitor/tracker.go
- Decisions0 to reviewMediumcmd/protocol-check/conformance.go0 awaiting review, 0 drifting from the code
- Ownership282 sole-owned filesMediumcmd/protocol-check/conformance.goOne author, no second reader