repowiserepowise
Sign in
shrutssss/cloudmind
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsContributorsDecisions
ChatPro
Stats
repowiserepowise
ExplorePricingDocs
Sign inIndex repoIndex your repo free
repowiseshrutssss/cloudmind

Commits

Every commit scored for change-risk against this repo's own history, so 'elevated' means elevated here rather than on some global curve.

Needs review

2of 4 scored

2 commits sit in this repo's top risk tercile, which is 50% of the 4scored. The cut is drawn against this codebase's own history rather than a global curve, so a quiet repo still fills its top band, and here it starts at 9.9 out of 10. What pushes a commit up is size and spread together: a large change confined to one area scores below a smaller one scattered across a dozen files.

Fix commits125%Commits whose subject reads as a bug fix rather than new work.Change diffusion0.83bitsShannon entropy of a commit's churn across its files. Zero is a single file, and every extra bit is a doubling of how widely the change spread.Review threshold9.9out of 10Score a commit has to clear to land in this repo's top tercile.

How the work changed shape

Commit categories over time, read off the subject line. Fixes carry the accent because that is the series this chart exists to show.

How this repo's commit mix shifts over time.

Feature25%
Fix25%
Other50%

Review-priority queue

Ranked by change-risk, highest first. Priority is a tercile of this repo's own distribution, so a quiet repo still fills its top band.

Commit review-priority queue
#CommitAuthorWhenLinesRiskTop driver
1
8f737177add project
shrutssss
1mo ago+45.9K -83
75%Elevated
more lines added than baseline
2
40b8ba25Initial project structure
shrutssss
1mo ago+9.5K -0
75%Elevated
more lines added than baseline
3
df6e2389changes1
shrutssss
1mo ago+2 -2
38%Typical
fewer lines added than baseline
4
4af0d75cfix issues
shrutssss
1mo ago+1 -1
13%Below typical
fewer lines added than baseline
  • 8f737177add project
    Author
    shrutssss
    When
    1mo ago
    Lines
    +45.9K -83
    Risk
    75%Elevated
  • 40b8ba25Initial project structure
    Author
    shrutssss
    When
    1mo ago
    Lines
    +9.5K -0
    Risk
    75%Elevated
  • df6e2389changes1
    Author
    shrutssss
    When
    1mo ago
    Lines
    +2 -2
    Risk
    38%Typical
  • 4af0d75cfix issues
    Author
    shrutssss
    When
    1mo ago
    Lines
    +1 -1
    Risk
    13%Below typical
Showing 4 of 4 commits

How the score behaves here

Change risk →

Two views of the same model: where the cuts fall, and what commit shape lands you above them.

Score distribution

Every scored commit, binned on the raw 0 to 10 score rather than the percentile. Percentile ranks are uniform by construction, so that axis has no shape to draw. The dashed lines are the tercile cuts behind each row's priority pill.

02typical ↑↑ elevated0.05.010.0Change-risk score →
Below typical
Typical
Elevated

Size against diffusion

The 4 most recent commits, on their own recency sample rather than the feed above: that defaults to risk-sorted, so reusing it would plot only the top tercile and call it the spread. Big and scattered is what the model penalises. Click a dot to open it.

1101001,00010,000Lines changed (log) →0.01.3Diffusion →
Below typical1
Typical1
Elevated2

Commit history for shrutssss/cloudmind

Repowise tracks change history across 46 files in shrutssss/cloudmind. In the last 90 days 46 files were touched, 51 times in total, most often main.py. Every commit is scored for change risk from its size, spread and the history of the files it touches.