change-impactcommit 4f08958SKILL.md · Architecture Tuning
Change Impact Analysis
Maps the impact surface from real dependencies before a change, then compares the actual diff with the plan afterwards.
npx skills add affaan-m/ECC --skill change-impactCommand selected. Copy it manually.
- Permissions
- read-repo
- write-files
- shell
- network
- Compatible with
- Claude Code, Codex, Cursor, Copilot, OpenCode
- GitHub
- 294.3k
- Source
- Community · Affaan Mustafa
- Status
- Scan passed
- License
- MIT
- Category
- Architecture Tuning
Core rule
Prove dependencies from real imports and calls, never from directory names; mark unknowns as unverified.
Execution Phases
Phase 01Establish evidence
Treat the request, repo docs and executable dependency evidence as truth, using git grep, git diff and tests.
Phase 02Map before the change
Answer code, data, interfaces, tests, documentation and release in order, including deploy order, compatibility window and rollback.
Phase 03Route decisions
Send durable decisions to ADRs, cross-client interfaces to contract-first, and regression to module checks; missing rollback info is a blocker.
Phase 04Align after implementation
Check whether the diff exceeds scope, evidence covers the success criteria, docs are in sync, and temporary code remains.
Permissions (summarised from SKILL.md)
| Capability | Needed | Details |
|---|---|---|
| File writes | Limited | Read-only by default; reports stay in the response, and a repo location is confirmed before writing. |
| Command execution | Limited | Gathers evidence with git grep, git diff and existing tests; other commands need host policy and explicit user approval. |
| Network outbound | Not required | No network access unless host policy allows it and the user explicitly approves. |
SKILL.md frontmatter (YAML)
---
name: change-impact
description: >-
Perform evidence-backed impact analysis before changing code, data, interfaces, or governance documents, then compare the planned impact with the actual diff after implementation. Covers call paths, data and schema, API contracts, tests, documentation, ADRs, deployment, migration, and rollback. Use for cross-module or high-risk changes, database migrations, authentication, public interfaces, blast-radius questions, pre-change checks, and post-implementation alignment.
---