repowiserepowise
Sign in
obra/superpowers
OverviewDocsArchitectureKnowledge GraphFilesCode HealthSecurityRefactoring

People & History

CommitsContributorsDecisions
Chat
Stats
repowiserepowise
ExplorePricingDocs
Sign in
repowiseobra/superpowers
SU
SU

obra / superpowers

shelljavascriptmain3dcbd5c28.9K linessynced 2mo ago

Code health

7.6out of 10Good

This codebase scores 7.6 out of 10 for code health, which we rate good. It also scores maintainability 8.7 and static performance 9.8 out of 10. The three are scored separately and never blended into one number. Risk is concentrated, as it usually is: 12 of 162 files are git hotspots, and they average 6.2 — which is where the fixes pay off most.

Full health report →
Documentation84pages0 with model-written prose, 84 built from the indexScore validation14/204.9× baselineTop-ranked files that did go on to need a bug fixDead code4exportsUnused exports that nothing in the graph reaches

Do next

1 thing worth doing this quarter.

Worth planning

  • Delete 4 unused symbols and files (119 lines)

    Nothing in the graph reaches them, across 2 files; every reader and agent pays to skip them.

    symbols
    4
    lines
    119
    safe to delete
    Yes(inferred)
    Small 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
  • Review the 40 proposed decisions

    None is accepted yet, so nothing can drift from one and agents get no enforced guidance from them.

    proposed
    40
    accepted
    0
    Medium effort
Lines of code
28.9K
Files
162
Symbols
327
Modules
6
Languages
4

Recent activity

All commits →

Commits

No commits indexed yet.

Decisions

  • Fire injection hook on every agent step (not only each turn)proposed · 2mo ago
  • Rely on Config.get() singleton to make live config modifications visibleproposed · 2mo ago
  • Inject bootstrap via first user message instead of system messageproposed · 2mo ago
  • Use module-level cache for bootstrap contentproposed · 2mo ago
  • Use portable /usr/bin/env bash shebang in shell scriptsproposed · 2mo ago
  • Increase configurable idle timeout and close WS on shutdownproposed · 2mo ago
▸

Everything we found

167 open

Every detector's open count by area, each with its worst example. An inventory, not a to-do list: the actions above are the part worth doing.

  • worst item is critical severity. Code health61Nested complexity · skills/brainstorming/scripts/server.cjs38 findings · 7.0 deducted→
  • worst item is medium severity. Refactoring5<anonymous>+1.5 health, M effort · skills/brainstorming/scripts/helper.js→
  • worst item is medium severity. Decisions52scripts/sync-to-codex-plugin.sh40 awaiting review · 12 hotspots ungoverned→
  • worst item is medium severity. Ownership43tests/codex/test-package-codex-plugin.sh98% single-owner concentration, 6 commits in 90d→
  • worst item is low severity. Dead code6skills/systematic-debugging/condition-based-waiting-example.tsUnreachable symbol (30 lines)→

Composition

Open the graph →
shell 72%javascript 22%
typescript 3%python 2%

Explore this codebase

  • Docs84 pages across 6 modules→
  • ChatAsk this codebase a question and get an answer with its sources.→
  • Files162 files with per-file docs, health and history→
  • ArchitectureDependency graph, layers, and 2 entry points→
  • Code healthPer-file scores, 118 open findings, coverage and refactoring targets→
  • Knowledge graphEntities, communities, and the paths between them→
  • Change couplingFiles that keep changing together, mined from commit history→
  • CommitsChange-risk ranked history with agent provenance→
  • ContributorsBus factor, per-file maintainers, and the human/agent split→
  • StatsSize class, origin, lifetime churn, rhythm and records→
  • CostsWhat indexing this snapshot cost, by model and by run.→