メニュー
Use when analyzing the impact of changing, renaming, or deleting a symbol. Provides risk assessment, blast radius, affected files, test coverage, and recommendations. Triggers for: "impact of changing X", "what would break if I modify X", "blast radius", "risk of renaming X", "safe to delete X"
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the user encounters Constellation errors, connection issues, or needs help debugging code intelligence problems. Triggers for: "Constellation errors", "fix Constellation", "debug Constellation", "Constellation not working", "API connection issues", "indexing problems", "MCP server issues", error codes like AUTH_ERROR, PROJECT_NOT_INDEXED
Use when getting a high-level overview of codebase architecture, project structure, language distribution, or understanding how the codebase is organized. Triggers for: "architecture overview", "codebase structure", "project summary", "language distribution", "how is this organized"
Use when analyzing file dependencies, checking for circular dependencies, or understanding what depends on a file. Supports forward (what does this file use?) and reverse (what uses this file?) analysis. Triggers for: "dependencies of X", "what imports this", "circular dependencies", "what depends on X", "dependency graph"
Use for a quick Constellation health check that tests MCP server connectivity, API authentication, and project indexing status. Triggers for: "diagnose Constellation", "health check", "why isn't code_intel working", "Constellation not responding", "check indexing status"
Use when checking Constellation API connectivity, authentication status, or verifying the code intelligence service is running. Triggers for: "is Constellation connected", "check API status", "verify authentication", "constellation status", "is code_intel working"
Use when finding dead code, orphaned exports, or unused functions/classes. Identifies exported symbols that are never imported anywhere in the codebase. Triggers for: "dead code", "unused exports", "orphaned code", "find unused functions", "clean up dead code"
| name | impact-analysis |
| description | Use when analyzing the impact of changing, renaming, or deleting a symbol. Provides risk assessment, blast radius, affected files, test coverage, and recommendations. Triggers for: "impact of changing X", "what would break if I modify X", "blast radius", "risk of renaming X", "safe to delete X" |
| allowed-tools | code_intel |
Analyze the impact of changing the specified symbol.
Arguments (provided by the user in natural language):
If no symbol name is provided, ask the user what symbol they want to analyze.
Call code_intel with this code parameter:
const result = await api.impactAnalysis({
symbolName: "<symbol-name>",
filePath: "<file-path>" || undefined,
depth: 3
});
return result;
If successful, present:
If high or critical risk, emphasize caution and suggest reviewing dependents before making changes.
If error, explain the error and provide guidance from the error response.