Help us improve
Share bugs, ideas, or general feedback.
From repowise
Assesses risk and impact before modifying, refactoring, or deleting files in a Repowise-indexed codebase. Flags hotspots, dependents, co-change patterns, and test gaps.
npx claudepluginhub repowise-dev/repowise --plugin repowiseHow this skill is triggered — by the user, by Claude, or both
Slash command
/repowise:pre-modificationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Before modifying files in a Repowise-indexed codebase, assess the impact.
Reviews code changes before merge using Repowise risk scoring and per-file directive analysis to identify breakage risks, missing co-changes, and test gaps.
Identifies riskiest codebase files using git churn analysis, complexity metrics, coupling, and lenskit risk scores for technical debt hotspots.
Analyzes impact of changes to files, APIs, components, or models. Provides dependency analysis, risk assessment, breaking changes, migration checklist, and test coverage gaps before modifications.
Share bugs, ideas, or general feedback.
Before modifying files in a Repowise-indexed codebase, assess the impact.
Call get_risk(targets=["path/to/file.py"]). Per file it returns
hotspot_score, trend, risk_type, impact_surface (top 3),
dependents_count, co_change_partners, primary_owner, bus_factor,
test_gap, and security_signals. Read it for:
hotspot_score, trend) — high-churn × complex? Extra care needed.dependents_count, impact_surface) — how wide is the blast radius?Batch all targets into one call: get_risk(targets=["file1.py", "file2.py", "module/"]).
If get_risk shows:
Call get_context(targets=["file.py"]) first to understand the full context: what uses this file, what decisions govern it, and why it's structured this way. This prevents accidentally violating architectural decisions.
For a heavy refactor, also call get_health(targets=["file.py"]) — the
biomarker findings (complexity, deep nesting, low cohesion, duplication) tell
you what to improve while you're in there, and give you a before/after score.
If get_risk returns a tool error, the MCP server may not be running. Proceed with the modification but note that risk assessment was unavailable.