What problem does it solve? Answering structural questions about a large codebase—blast radius of a change, module ownership, endpoint exposure, orphaned message contracts, RBAC coverage—normally requires slow, error-prone grepping across many projects. This Skill answers those questions by querying a code-derived Neo4j knowledge graph through ten fixed, read-only MCP tools instead of reading source files. ## Core Features & Use Cases - Impact and dependency analysis: Use GetBlastRadius and GetNodeDependencies to see what a change affects or what a node needs to run, with configurable depth. - Architecture and contract auditing: Use GetModuleDependencies, GetModuleOwnership, and GetOrphanContracts to map bounded-context integration and find dead message/query contracts with confidence levels. - Exposure, jobs, and RBAC: Use GetActionExposure, GetJobSchedulers, GetGovernedActions, and FindStructurallySimilarActions to trace endpoint/page wiring, job scheduling, authorization coverage, and reusable patterns. - Use Case: Before renaming an OrderService method, ask what breaks—the Skill calls GetBlastRadius on the fully-qualified node id and returns a markdown table of every affected endpoint, page, handler, and job. ## Quick Start Ask the assistant to use the ecommerceapp-kg-query skill to show the blast radius of changing ECommerceApp.Application.Orders.OrderService.PlaceOrder.
