pre-modification-check
The pre-modification-check skill uses Repowise's codebase graph and git signals to assess modification risk before editing files. Call `get_risk()` to evaluate hotspot status, dependents, co-change patterns, ownership, and test coverage, then warn the user when hotspot scores exceed the 90th percentile, more than ten dependents exist, bus factor equals one, or risk factors like bug-proneness appear. Use `get_context()` before refactoring or moving code to understand dependencies and structural decisions.
git clone --depth 1 https://github.com/repowise-dev/repowise /tmp/pre-modification-check && cp -r /tmp/pre-modification-check/plugins/codex/skills/pre-modification-check ~/.claude/skills/pre-modification-checkSKILL.md
# Pre-Modification Check With Repowise Before editing a Repowise-indexed codebase, assess impact with the graph and git signals. ## Before Editing Files Call `get_risk(targets=["path/to/file.py"])` to understand: - Hotspot status and churn trend. - Dependents and likely blast radius. - Co-change partners that may need updates. - Ownership and recommended review context. - Bus factor and maintenance concentration. - Test gaps or security signals. ## When Editing Multiple Files Batch all targets in one call: `get_risk(targets=["file1.py", "file2.py", "module/"])`. ## When To Warn The User Warn before editing when `get_risk` shows: - Hotspot score above the 90th percentile. - More than 10 dependents. - Bus factor of 1. - Risk type such as `bug-prone` or `high-coupling`. - Missing tests around changed or affected files. ## Before Refactoring Or Moving Code Call `get_context(targets=["path/to/file.py"])` first to understand what uses the file, which decisions govern it, and why it is structured that way. ## Error Handling If `get_risk` fails or the MCP server is unavailable, proceed with normal inspection and mention that Repowise risk assessment was unavailable.
Use when a task asks why code is built a certain way, proposes architectural changes, compares implementation approaches, or mentions decision markers such as WHY, DECISION, TRADEOFF, or ADR in a Repowise-indexed repository.
>
>
Use when exploring, understanding, or answering questions about a Repowise-indexed codebase, including architecture, where code is implemented, how a module works, or which files are relevant before reading source.
Use when the user asks about unused code, cleanup, deleting files or exports, refactoring old areas, reducing bundle size, code hygiene, technical debt, or maintenance in a Repowise-indexed repository.