repowisehexsleeves/happy

HexSleeves / happy

typescriptmainb824cd0214.3K linessynced 1mo ago

Code health

6.9out of 10Fair

Hotspots average 4.3, the place fixes pay off most.

Full health report
Documentation1,470pages
0 with model-written prose, 1,470 built from the indexScore validation18/203.3× baselineTop-ranked files that did go on to need a bug fix

Explore this codebase

AlsoDocsChatFilesKnowledge graphChange couplingCommitsStatsCosts

Do next · 3

3 things worth doing in the week to Aug 28, the last indexed commit.

Worth planning

  • Start breaking up reducer (CCN 210, 699 lines): first lift lines 748-851

    packages/happy-app/sources/sync/reducer/reducer.ts:748

    reducer nests deeply; easier to read and change once split, which also removes a duplicate; function changed in 39 commits; its file is imported by 4 files, changed 5 times in 90 days.

    gain
    up to +1.6 health on this file(inferred)
    finding
    Nested complexity
    size
    CCN 210, 699 lines, nests 9 deep
    severity
    high
    worth a check

  • Start breaking up startDaemon (CCN 114, 704 lines): first lift lines 62-1032

    packages/happy-cli/src/daemon/run.ts:62

    startDaemon nests deeply; easier to read and change once split, which also removes a duplicate; function changed in 52 commits; its file is imported by 7 files, changed 8 times in 90 days.

    gain
    up to +1.8 health on this file(inferred)
    finding
    Nested complexity
    size
    CCN 114, 704 lines, nests 7 deep
    severity
    high
    worth a check

  • Start breaking up runCodex (CCN 138, 786 lines): first lift lines 143-156

    packages/happy-cli/src/codex/runCodex.ts:143

    runCodex nests deeply; easier to read and change once split, which also removes a duplicate; function changed in 52 commits; its file is imported by 1 file, changed 14 times in 90 days.

    gain
    up to +1.1 health on this file(inferred)
    finding
    Nested complexity
    size
    CCN 138, 786 lines, nests 5 deep
    severity
    high
    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

Everything we found

5 areas

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