القائمة
Use when user asks what breaks if I change X, impact of changing, what depends on, trace data flow, show connections, dependency graph, upstream/downstream, or safe to modify before refactoring.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when user asks to show or generate an architecture diagram, visualize dependencies, export architecture docs, create architecture documentation, save architecture output, or create a mermaid diagram of their project.
Use when user asks to scan architecture, check dependencies, find outdated packages, show project structure, refresh architecture, or run a health check. Navgator scan, status, and staleness check.
Use when user asks to review architecture, check connections, navgator review, is this safe to merge, what did I break, or when scan detects architectural drift. Architectural integrity review of system flow and connections.
Detect and analyze infrastructure components — Prisma models, env vars, queues, crons, deploy configs, field usage, and type validation
Use when user asks to install navgator, update navgator, set up navgator, launch the dashboard, or run navgator ui maintenance.
| name | impact-analysis |
| description | Use when user asks what breaks if I change X, impact of changing, what depends on, trace data flow, show connections, dependency graph, upstream/downstream, or safe to modify before refactoring. |
| version | 0.9.1 |
| user-invocable | false |
Analyze what's affected by changes and map component connections using NavGator MCP tools. This skill covers impact analysis, connection viewing, and dataflow tracing.
Use the navgator impact MCP tool with the component name to analyze blast radius.
Input: Component name (e.g., "express", "prisma", "/api/users")
Returns:
If the user provides a file path instead of a component name:
Use the navgator connections MCP tool to show all connections for a component.
Input: Component name (required), direction (optional: "in", "out", or "both")
Returns:
Use the navgator trace MCP tool to follow data flow through the architecture.
Input: Component name (required), direction (optional: "forward", "backward", or "both")
Returns:
| User Intent | MCP Tool | Notes |
|---|---|---|
| "What breaks if I change X?" | navgator impact | Full blast radius |
| "Show connections for X" | navgator connections | All connections |
| "What depends on X?" | navgator connections (direction: "in") | Incoming only |
| "What does X use?" | navgator connections (direction: "out") | Outgoing only |
| "Trace data flow from X" | navgator trace | Forward/backward/both |
| "Is it safe to modify X?" | navgator impact | Check severity |
Present results clearly:
navgator — architecture tracker
