repowisexmokecursed/xtify

xmokecursed / xtify

dartmain1d85ebf8.4K linessynced on Oct 30, 2026

Code health

6.7out of 10Fair

Hotspots average 4.9, the place fixes pay off most.

Full health report
Documentation96pages
0 with model-written prose, 96 built from the indexScore validation5/202.8× baselineTop-ranked files that did go on to need a bug fix

Explore this codebase

AlsoDocsChatFilesKnowledge graphChange couplingCommitsStatsCosts

Do next · 2

2 things worth doing in the week to Oct 29, the last indexed commit.

Worth planning

  • Break up _loadPool (CCN 40, 91 lines)

    lib/services/auto_queue_service.dart:172

    _loadPool has many paths; easier to read and change once split; its file is imported by 2 files, changed 4 times in 90 days.

    gain
    up to +1.9 health on this file(inferred)
    finding
    Complex method
    size
    CCN 40, 91 lines
    severity
    high
    worth a check

  • Tidy the code shape this week's commits left: 18 findings in 10 files

    10 commits in the last 7 days added or worsened long, complex or deeply nested code, still open. Start with lib/services/audio_service.dart (4 findings): tidying it while the change is fresh costs less than after the next one.

    code-shape findings
    18
    files
    10
    commits
    10

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

Everything we found

4 areas

Every detector's open count by area. The actions above are the part worth doing.