Verified:GitHub

repository-area-impact-planner

Maps files, APIs, tests, and docs affected by a proposed repository change.

Updated Jul 7, 2026

Search Tags:#code review #impact analysis #dependency tracing #repository analysis #test planning #blast radius #change planning

Ready to run

npx skills add https://github.com/vmitsaras/Agent-Skills --skill repository-area-impact-planner-vmitsaras

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: repository-area-impact-planner
Source: https://github.com/vmitsaras/Agent-Skills/tree/main/skills/project-planning/repository-area-impact-planner
Command: npx skills add https://github.com/vmitsaras/Agent-Skills --skill repository-area-impact-planner-vmitsaras

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before implementing a change, developers often guess which files, modules, tests, and docs will be affected, leading to missed updates and regressions. This Skill produces an evidence-backed impact map of the repository blast radius before any code is edited. ## Core Features & Use Cases - Blast-Radius Analysis: Traces imports, exports, callers, public contracts, schemas, routes, and config keys to identify confirmed, likely, and possible affected areas. - Test and Docs Impact Mapping: Identifies existing tests to update, missing coverage to add, and documentation, examples, or demos that need changes. - Structured Impact Plan: Outputs a prioritized file checklist, validation plan, risk register, and open questions ready for a maintainer or coding agent. - Use Case: Before changing a public API response shape, ask for an impact map to see which consumers, fixtures, migration notes, and CI checks must be updated. ## Quick Start Ask the agent to map the blast radius of your proposed change and list the files, tests, and docs likely affected before implementation.

Frequently Asked Questions about repository-area-impact-planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I find which files are affected by a code change?▼

Provide the proposed change and let the planner trace imports, exports, callers, and consumers around the target area. It returns an impact map listing affected files and modules with evidence, confidence levels, and recommended actions.

What is blast-radius analysis in software development?▼

Blast-radius analysis predicts the downstream impact of a change across source code, public APIs, tests, docs, and configuration before implementation. It helps maintainers sequence work, spot regression risks, and avoid missed updates.

Does impact analysis work in a monorepo?▼

Yes. The planner identifies the target package, shared packages, cross-package contracts, and workspace-level checks before listing files, so cross-boundary impacts in monorepos are captured explicitly.

When should I not use repository impact planning?▼

Skip it when you want immediate implementation without a planning artifact, when the request is feature prioritization or roadmap sequencing, or when no repository context is available for evidence-based analysis.

How does impact analysis handle generated files?▼

The planner distinguishes generated artifacts from source-of-truth files and locates the generator or source definition before recommending edits, so you avoid editing lockfiles or build outputs directly.