code-analysis

Plugin code-analysis from marketplace mag-claude-plugins in MadAppGang/claude-code. Commands read from the repo's manifest — 1 month ago.

Skills (13)

• architect-detective

  Use when analyzing architecture and system design. Find design patterns, map layers, identify core abstractions via PageRank. Uses claudemem AST structural analysis for efficient architecture investigation.

• claudemem-orchestration

  Use when orchestrating multi-agent code analysis with claudemem. Run claudemem once, share output across parallel agents. Enables parallel investigation, consensus analysis, and role-based command mapping.

• claudemem-search

  ⚡ PRIMARY TOOL for semantic code search AND structural analysis. NEW: AST tree navigation with map, symbol, callers, callees, context commands. PageRank ranking. Recommended workflow: Map structure first, then search semantically, analyze callers before modifying.

• claudish-usage

  CRITICAL - Guide for using Claudish CLI ONLY through sub-agents to run Claude Code with OpenRouter models (Grok, GPT-5, Gemini, MiniMax). NEVER run Claudish directly in main context unless user explicitly requests it. Use when user mentions external AI models, Claudish, OpenRouter, or alternative mo

• code-search-selector

  💡 Tool selector for code search tasks. Helps choose between semantic search (claudemem) and native tools (Grep/Glob) based on query type. Semantic search recommended for: 'how does X work', 'find all', 'audit', 'investigate', 'architecture'.

• cross-plugin-detective

  Use when integrating detective skills across plugins. Maps agent roles to appropriate detective skills (developer → developer-detective, architect → architect-detective). Reference this to connect agents with claudemem investigation capabilities.

• debugger-detective

  ⚡ Debugging skill. Best for: 'why is X broken', 'find bug source', 'root cause analysis', 'trace error', 'debug issue'. Uses claudemem AST with context command for efficient call chain analysis.

• deep-analysis

  ⚡ PRIMARY SKILL for: 'how does X work', 'investigate', 'analyze architecture', 'trace flow', 'find implementations'. PREREQUISITE: code-search-selector must validate tool choice. Launches codebase-detective with claudemem INDEXED MEMORY.

• developer-detective

  ⚡ Implementation analysis skill. Best for: 'how does X work', 'find implementation of', 'trace data flow', 'where is X defined', 'find all usages'. Uses claudemem AST with callers/callees for efficient code tracing.

• investigate

  Unified entry point for code investigation. Auto-routes to specialized detective based on query keywords. Use when investigation type is unclear or for general exploration.

• search-interceptor

  💡 Bulk file read optimizer. Suggests semantic search alternatives when reading multiple files. Helps reduce token usage by using claudemem's ranked results instead of sequential file reads.

• tester-detective

  ⚡ Test analysis skill. Best for: 'what's tested', 'find test coverage', 'audit test quality', 'missing tests', 'edge cases'. Uses claudemem AST with callers analysis for efficient test discovery.

• ultrathink-detective

  ⚡ Comprehensive analysis skill. Best for: 'comprehensive audit', 'deep analysis', 'full codebase review', 'multi-perspective investigation', 'complex questions'. Combines all perspectives (architect+developer+tester+debugger). Uses Opus model with full claudemem AST analysis.

Slash commands (3)

• /code-analysis:analyze

  Deep codebase investigation to understand architecture, trace functionality, find implementations, and analyze code patterns

• /code-analysis:help

  Show comprehensive help for the Code Analysis Plugin - lists agents, commands, skills, and usage examples

• /code-analysis:setup

  Add claudemem enforcement rules to project CLAUDE.md and verify setup

Subagents (1)

• detective

  Use this agent when you need to investigate, analyze, or understand patterns in a codebase. This includes finding specific implementations, understanding code relationships, discovering usage patterns, tracking down bugs, analyzing architecture decisions, or investigating how certain features work.

MCP servers (1)

• claudish

  runs: claudish --mcp

Hooks (4)

• SessionStart

  bun "${CLAUDE_PLUGIN_ROOT}/hooks/handler.ts"

• PreToolUse

  bun "${CLAUDE_PLUGIN_ROOT}/hooks/handler.ts"

• PreToolUse

  bun "${CLAUDE_PLUGIN_ROOT}/hooks/handler.ts"

• PostToolUse

  bun "${CLAUDE_PLUGIN_ROOT}/hooks/handler.ts"

Similar plugins