repowiserepowise
Sign in
subhasis-hacker/code-reviewer
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsContributorsDecisions
ChatPro
Stats
repowiserepowise
ExplorePricingDocs
Sign inIndex repoIndex your repo free
repowisesubhasis-hacker/code-reviewer

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 6 scored

2 commits sit in this repo's top risk tercile, which is 33% of the 6scored. 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.7 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 commits00%Commits whose subject reads as a bug fix rather than new work.Change diffusion2.15bitsShannon 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.7out 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.

Feature50%
Docs33%
Other17%

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
33b5d3bfinitial commit to github
Subhasis-hacker
2w ago+5.1K -0
92%Elevated
more lines added than baseline
2
0f6a3ae0work on cp platform adding feature
Subhasis-hacker
2d ago+2.3K -18
75%Elevated
more lines added than baseline
3
ab060070add authuntication
Subhasis-hacker
1d ago+1.2K -9
58%Typical
more lines added than baseline
4
8438eef8add readme.md file
SUBHASIS CODER
2w ago+210 -0
42%Typical
more lines added than baseline
5
547f9e59Update backend services and add gitignore for frontend build files
Subhasis-hacker
2w ago+117 -53
25%Below typical
more lines added than baseline
6
633b4728Remove README and .gitignore
Subhasis-hacker
2w ago+0 -250
8%Below typical
fewer lines added than baseline
  • 33b5d3bfinitial commit to github
    Author
    Subhasis-hacker
    When
    2w ago
    Lines
    +5.1K -0
    Risk
    92%Elevated
  • 0f6a3ae0work on cp platform adding feature
    Author
    Subhasis-hacker
    When
    2d ago
    Lines
    +2.3K -18
    Risk
    75%Elevated
  • ab060070add authuntication
    Author
    Subhasis-hacker
    When
    1d ago
    Lines
    +1.2K -9
    Risk
    58%Typical
  • 8438eef8add readme.md file
    Author
    SUBHASIS CODER
    When
    2w ago
    Lines
    +210 -0
    Risk
    42%Typical
  • 547f9e59Update backend services and add gitignore for frontend build files
    Author
    Subhasis-hacker
    When
    2w ago
    Lines
    +117 -53
    Risk
    25%Below typical
  • 633b4728Remove README and .gitignore
    Author
    Subhasis-hacker
    When
    2w ago
    Lines
    +0 -250
    Risk
    8%Below typical
Showing 6 of 6 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.

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

Size against diffusion

The 6 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,000Lines changed (log) →0.04.1Diffusion →
Below typical2
Typical2
Elevated2

Commit history for subhasis-hacker/code-reviewer

subhasis-hacker/code-reviewer has 6 commits in its history from 2 contributors, the first of them Jul 30, 2026. In the last 90 days 51 files were touched, 59 times in total, most often config.py. Every commit is scored for change risk from its size, spread and the history of the files it touches.