repowiserepowise
Sign in
dguz317/local-coding-tool
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsContributorsDecisions
ChatPro
Stats
repowiserepowise
ExplorePricingDocs
Sign inIndex repoIndex your repo free
repowisedguz317/local-coding-tool
LO
LO

dguz317 / local-coding-tool

markdownmain1ed774648.3K linessynced 7h ago

Code health

5.6out of 10Fair

This codebase scores 5.6 out of 10 on defect risk, which we rate fair. It also scores maintainability 6.8 and static performance risk 9.8 out of 10. The three are scored separately and never blended into one number. The files you change most are the weak spot: 23 of 165 files are git hotspots, and they average 3.1.

Full health report →
Documentation113pages0 with model-written prose, 113 built from the indexScore validation8/206× baselineOf the 20 lowest-health files, 8 were bug-fixed in the last 6 months — 6× the 7% baseline
Lines of code
48.3K
Files
165
Symbols
1,620
Modules
40
Languages
6

Recent activity

All commits →

Commits

No commits indexed yet.

Decisions

  • Introduce a graph-store seam to centralize artifact lifecycle and SQLite readsproposed · 7h ago
  • Layered local code intelligence engineproposed · 7h ago
  • Avoid implying stronger certainty than graph evidence supportsproposed · 7h ago
  • Separate evidence concepts for package identity, ownership, and resolutionproposed · 7h ago
  • Store ambiguous relationships as candidates (not graph edges)proposed · 7h ago
  • Rely on ranking and progressive disclosure for context economyproposed · 7h ago

Needs attention

93 open
  • medium severity. ProposedIntroduce a graph-store seam to centralize artifact lifecycle and SQLite readsAuto-proposed decision awaiting review
  • medium severity. ProposedLayered local code intelligence engineAuto-proposed decision awaiting review
  • medium severity. ProposedAvoid implying stronger certainty than graph evidence supportsAuto-proposed decision awaiting review
  • medium severity. ProposedSeparate evidence concepts for package identity, ownership, and resolutionAuto-proposed decision awaiting review
  • medium severity. ProposedStore ambiguous relationships as candidates (not graph edges)Auto-proposed decision awaiting review

Where the risk concentrates

All 23 hotspots →

Ranked by prior bug fixes and change frequency, mined from full git history rather than from the code alone.

FileChurnPrior fixesMaintainersCommits 90d
graph.pysrc/repolens98.9th5bug magnet1bus factor 134
query.pysrc/repolens97.8th01bus factor 120
context_pack.pysrc/repolens96.8th01bus factor 118
javascript_index.pysrc/repolens95.7th21bus factor 111
semantic_artifact.pysrc/repolens94.6th01bus factor 19

Composition

Open the graph →
markdown 61%python 35%yaml 2%dockerfile 1%toml 1%Other 1%

Explore this codebase

  • Docs113 pages across 40 modules→
  • ChatAsk this codebase a question and get an answer with its sources→
  • Files165 files with per-file docs, health and history→
  • ArchitectureDependency graph, layers, and 1 entry points→
  • Code healthPer-file scores, 555 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→