Determine what code changes will affect and find dependencies using DevAC's Analytics Layer.
Analyzes code dependencies and change impact using DevAC's analytics layer. Activates when users ask "what will this affect", "find dependencies", or "show call graph" to trace upstream/downstream impacts before refactoring.
/plugin marketplace add pietgk/vivief/plugin install devac@viviefThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Determine what code changes will affect and find dependencies using DevAC's Analytics Layer.
This skill activates when users ask about:
Determine which files would be impacted by changes to a specific file or symbol.
Trace dependencies both upstream (what this depends on) and downstream (what depends on this).
Understand how functions call each other throughout the codebase.
Before making changes, understand the blast radius.
Use DevAC CLI commands for impact analysis. CLI is preferred for lower context overhead.
devac affectedGet files that would be affected by changes to a specific file.
devac affected src/core/auth.ts
devac affected src/services/user.ts --depth 2
devac depsGet dependencies of a specific file or symbol.
devac deps src/services/user.ts
devac deps src/core/auth.ts --direction both
devac call-graphGet the call graph for a specific function or method.
devac call-graph validateUser --depth 3
devac call-graph login --direction callers
devac queryAdvanced queries for complex dependency analysis.
devac query "SELECT DISTINCT callee_symbol, callee_file FROM calls WHERE caller_file = 'src/core/auth.ts'"
User: "What will be affected if I change the UserService class?"
Response approach:
devac affected src/services/user.ts to find impacted filesdevac call-graph UserService to show function-level impactUser: "Show me the call graph for the login function"
Response approach:
devac find-symbol login to locate the functiondevac call-graph login --depth 3User: "What are the dependencies of the payment module?"
Response approach:
devac deps src/payment/ on payment module filesIf MCP server is configured, these tools provide equivalent functionality:
get_affectedget_affected(file_path: "src/core/auth.ts")
get_dependenciesget_dependencies(file_path: "src/services/user.ts")
get_call_graphget_call_graph(symbol: "validateUser", depth: 3)
query_sqlSELECT DISTINCT callee_symbol, callee_file
FROM calls
WHERE caller_file = 'src/core/auth.ts'
devac analyzeThis skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.