Analyze code structure, find symbols, and explore hierarchies using DevAC's Analytics Layer.
Analyze code structure, find symbols, and explore hierarchies using DevAC's Analytics Layer.
/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.
Analyze code structure, find symbols, and explore hierarchies using DevAC's Analytics Layer.
This skill activates when users ask about:
Find and explore symbols (functions, classes, methods, variables) across the codebase.
Understand inheritance, composition, and module structure.
Get an overview of how code is organized within files and across the project.
Use DevAC CLI commands for code analysis. CLI is preferred for lower context overhead.
devac find-symbolFind symbols by name across all indexed repositories.
devac find-symbol UserService
devac find-symbol --kind class Controller
devac file-symbolsGet all symbols defined in a specific file or directory.
devac file-symbols src/services/user.ts
devac file-symbols src/auth/
devac queryRun SQL queries against the Seeds database for advanced analysis.
devac query "SELECT name, kind, file_path FROM symbols WHERE kind = 'class' ORDER BY name"
devac query "SELECT * FROM symbols WHERE name LIKE '%UserService%'"
User: "What functions are defined in the auth module?"
Response approach:
devac file-symbols src/auth/ to list all symbolsUser: "Show me the class hierarchy for BaseController"
Response approach:
devac find-symbol BaseControllerdevac queryIf MCP server is configured, these tools provide equivalent functionality:
find_symbolfind_symbol(name: "UserService")
get_file_symbolsget_file_symbols(file_path: "src/services/user.ts")
query_sqlSELECT name, kind, file_path
FROM symbols
WHERE kind = 'class'
ORDER BY name
devac hub init)devac analyze .)This 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.