Impact Analysis

Trace downstream dependencies and report file:line citations for monorepo changes.

1|1|Updated Mar 31, 2026

Search Tags:#openapi #dependencies #review #impact-analysis #downstream #fedramp

Ready to run

npx skills add https://github.com/btabaska/simpler-grants-documentation-automation --skill impact-analysis-btabaska

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Impact Analysis
Source: https://github.com/btabaska/simpler-grants-documentation-automation/tree/main/.cursor/skills/skill-impact-analysis
Command: npx skills add https://github.com/btabaska/simpler-grants-documentation-automation --skill impact-analysis-btabaska

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze the blast radius of a proposed change across the simpler-grants-gov monorepo. Triggers on phrases like 'impact analysis', 'what does this break', 'who depends on', or before merging changes that touch shared modules, API schemas, database models, or frontend hooks. Reports downstream callers, cross-service contracts, and FedRAMP-relevant boundaries with file:line citations.

Core Features & Use Cases

The skill identifies direct callers, transitive consumers, schema-coupled artifacts (OpenAPI, Alembic, frontend types), and crosses the API/frontend boundary so reviewers do not have to grep blind.

Quick Start

Invoke the Impact Analysis skill on a pull request by specifying the changed target path and optional scope and depth.

Frequently Asked Questions about Impact Analysis

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

FAQPage Schema

How do I analyze the blast radius of code changes across a monorepo?▼

Blast radius analysis traces direct and transitive dependencies affected by code changes across a monorepo. It identifies downstream callers, schema-coupled artifacts, and cross-service contracts with file:line citations to ensure safe merges.

How do I check downstream dependencies before merging OpenAPI schema changes?▼

Checking downstream dependencies before merging OpenAPI schema changes involves tracing transitive consumers and frontend type implications. This impact analysis surfaces schema-coupled artifacts and reports FedRAMP-relevant boundaries with precise file:line citations.

What is the best way to identify transitive callers when modifying shared modules?▼

Identifying transitive callers when modifying shared modules requires tracing direct callers and their downstream consumers. This process surfaces cross-service contracts and FedRAMP-relevant boundaries, preventing blind grep searches during pull request triage.

Can I trace database model changes to frontend hooks during PR triage?▼

Yes, you can trace database model changes to frontend hooks during PR triage. This impact analysis crosses the API and frontend boundaries to identify coupled artifacts, direct callers, and transitive dependencies with file:line citations.

When do I need to run an impact analysis on a pull request?▼

You need to run an impact analysis when a pull request touches shared modules, API schemas, database models, or frontend hooks. It is useful for pre-merge checks, risk assessment, and identifying FedRAMP-relevant boundaries.

Why does modifying shared modules break downstream consumers without warning?▼

Modifying shared modules breaks downstream consumers when transitive dependencies and cross-service contracts are not traced beforehand. Impact analysis identifies these schema-coupled artifacts and FedRAMP-relevant boundaries to prevent unexpected failures.