repowiserepowise
Sign in
2233admin/AxisAgentic
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsContributorsDecisions
ChatPro
Stats
repowiserepowise
ExplorePricingDocs
Sign inIndex repoIndex your repo free
repowise2233admin/AxisAgentic

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

1of 3 scored

1 commits sit in this repo's top risk tercile, which is 33% of the 3scored. 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 10.0 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 diffusion3.64bitsShannon 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 threshold10.0out 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.

Feature33%
Docs33%
Chore33%

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
337d5fc8feat: initialize AxisAgentic runtime and evaluation framework
Wang, Jinyu
1w ago+64.1K -0
83%Elevated
more lines added than baseline
2
f4512232chore: refine AxisAgentic positioning and benchmark configuration
Wang, Jinyu
1w ago+484 -118
50%Typical
more lines added than baseline
3
0aa54b14docs: clarify runtime and trajectory collection positioning
Wang, Jinyu
1w ago+39 -42
17%Below typical
more lines added than baseline
  • 337d5fc8feat: initialize AxisAgentic runtime and evaluation framework
    Author
    Wang, Jinyu
    When
    1w ago
    Lines
    +64.1K -0
    Risk
    83%Elevated
  • f4512232chore: refine AxisAgentic positioning and benchmark configuration
    Author
    Wang, Jinyu
    When
    1w ago
    Lines
    +484 -118
    Risk
    50%Typical
  • 0aa54b14docs: clarify runtime and trajectory collection positioning
    Author
    Wang, Jinyu
    When
    1w ago
    Lines
    +39 -42
    Risk
    17%Below typical
Showing 3 of 3 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.

01↑ typical0.05.010.0Change-risk score →
Below typical
Typical
Elevated

Size against diffusion

The 3 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.06.2Diffusion →
Below typical1
Typical1
Elevated1

Commit history for 2233admin/AxisAgentic

2233admin/AxisAgentic has 3 commits in its history from 1 contributor, the first of them Jul 23, 2026. In the last 90 days 167 files were touched, 169 times in total, most often setup.py. Every commit is scored for change risk from its size, spread and the history of the files it touches.