repowisegithub/spec-kit

github / spec-kit

pythonmain08252af225.1K linessynced on Nov 10, 2026

Code health

7.6out of 10Good

Hotspots average 6.6, the place fixes pay off most.

Explore this codebase

Do next · 2

2 things worth doing in the week to Nov 10, the last indexed commit.

Worth planning

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

    6 commits in the last 7 days added or worsened long, complex or deeply nested code, still open. Start with extensions/git/scripts/python/create_new_feature_branch.py (1 finding): tidying it while the change is fresh costs less than after the next one.

    code-shape findings
    8
    files
    8
    commits
    6
  • Review why fixes keep landing in src/specify_cli/workflows/engine.py: tests reach it

    Changed 13 times in 90 days, and 4 of those commits were bug fixes.

    commits in 90 days
    13
    bug-fix commits
    4
    line coverage
    Unknown, no report
    tests that reach it
    18 test files, call graph(inferred)
    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