# Change Review

Use when reviewing a set of changes before they merge, a PR, a branch diff, or the...

- Repository: https://github.com/repowise-dev/repowise (8087 stars)
- Category: Git and review
- License: AGPL-3.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add repowise-dev/repowise --skill change-review -g -a claude-code -y`
Codex: `npx skills add repowise-dev/repowise --skill change-review -g -a codex -y`
Cursor: `npx skills add repowise-dev/repowise --skill change-review -g -a cursor -y`
Gemini CLI: `npx skills add repowise-dev/repowise --skill change-review -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add repowise-dev/repowise`

## Description

Use when reviewing a set of changes before they merge, a PR, a branch diff, or the working-tree changes you just made, in a Repowise-indexed codebase (.repowise/ directory exists). Activates for "review this PR", "is this safe to merge", "what's the blast radius of these changes", "did I miss anything", or "what else should change with this".

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Change Review with Repowise

When a diff is on the table, Repowise turns "what files changed" into "what does
this change put at risk", fusing git history (churn, ownership, co-change) with
graph topology (dependents, impact surface), test gaps, security signals, and the
architectural decisions that govern the touched code.

Two complementary risk signals, use both:

- **`get_change_risk(revspec=…)` (MCP)** scores the *whole change as one unit* (a
  commit or a `base..head` range). No LLM, no network. Prefer this in-MCP
  tool; it takes a revspec and diffs server-side, so you never shell out. Lead
  with `directive` and `health_delta`, what the change actually made worse.
  Findings the change wrote sort above pre-existing ones it only touched.
  Then `risk_percentile` (this change ranked against sampled recent commits by
  diff size and spread, not a bug predictor), stated in one line by
  `diff_shape`; `include=["scales"]` adds its `review_priority` tercile and
  `classification` label. The raw 0-10 `score`
  ranks 0.99 against lines added, so it sits behind `include=["diagnostics"]`
  rather than on the wire.
  Omit `revspec` to score uncommitted work. This is the pre-merge gate: "how risky is this
  change overall?" The `repowise risk <revspec>` CLI is the identical scorer for
  when you are already in a terminal.
- **`get_risk(changed_files=…)` (MCP)** works *per file* and returns the
  `directive` block, the specific things to check inside the diff.

## Score the whole change first

```
get_change_risk(revspec="main..HEAD")   # HEAD, a commit SHA, or base..head
```

The rest: https://github.com/repowise-dev/repowise/blob/HEAD/plugins/claude-code/skills/change-review/SKILL.md