change-impact-checker

Evaluate likely change impact before edits and command execution.

IndexedMIT★ 1

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/alubiama-change-impact-checker

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Evaluate likely change impact before edits and command execution. Use when modifying code, configs, infra, automation, or dependencies. Highlight affected components, regression risk, and validation needs.

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/change-impact-checker

What's inside

Skill name: change-impact-checker
Description: Evaluate likely change impact before edits and command execution. Use when modifying code, configs, infra, automation, or dependencies. Highlight affected components, regression risk, and validation needs.
License: MIT
Instructions: 35 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

# Change Impact Checker

## Goal

Catch regressions early by mapping blast radius before changes.

## Impact Workflow

1. Identify target files/components.
2. Map direct and indirect dependencies.
3. Estimate regression risk (`low/medium/high`).
4. Define required tests/checks before and after.
5. Recommend smallest safe change order.

## Risk Signals

- Touching shared libraries or critical paths.
- Changing auth, billing, state, data writes, or scheduling.
- Updating dependencies with unknown compatibility.

## Output Contract

Always output:

1. `affected_components`
2. `risk_level`
3. `required_validation`
4. `safe_change_order`

## Guardrails

- Do not skip validation steps for medium/high impact changes.
- Escalate uncertainty when impact cannot be estimated confidently.

From Alubiama/awesome-cognitive-skills, MIT.

Signals

Stars: 1
Forks: 0
Open issues: 0
Last commit (this folder): Mar 22, 2026 (7 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/Alubiama/awesome-cognitive-skills
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from Alubiama

Cite this page

change-impact-checker skill. Agent Mart. https://agentmart.dev/skills/alubiama-change-impact-checker (last updated 2026-10-24)