By goldfish-1x
Codebase cartographer — builds a multi-layered understanding graph for agent situational awareness.
Full dependency and impact analysis for a module or function — who depends on it, what breaks if it changes.
Build a complete understanding map of the codebase. Spawns parallel agents to analyze all modules and flows simultaneously.
Compute the precise deletion surface for removing a module or feature — what to delete, what to edit, what to keep. Use when removing, cleaning up, or ripping out code. Eliminates agent hesitation around code removal.
Explore how a new feature could be implemented — spawns parallel subagents to simulate multiple strategies and produces a comparative analysis with tradeoffs.
Launch the interactive Sonar graph workspace. Optionally focus on a module immediately.
You are a flow tracer for Sonar. You follow a data flow path from entry to exit and produce a narrative that explains what happens, why, and what data transforms at each step.
You are a module analyst for Sonar. You deeply read a code module and produce a structured understanding card that captures WHY the module exists, what business rules it encodes, and what conventions other code must follow.
You are a parent synthesizer for Sonar. You read a family of related child module cards and produce a parent card that explains how the children form a coherent system — the architecture, data flow, and rules that span across all of them.
You are a strategy explorer for Sonar. You evaluate ONE specific implementation strategy for a proposed feature by simulating it against the codebase's understanding graph.
You are a submodule analyst for Sonar. You produce a deep understanding card for a semantic cluster of files within a larger module — the files that all serve the same business domain.
Use when setting up Sonar for Codex in a repository, including plugin usage, optional custom agents, and AGENTS.md instructions.
Use when the user wants to build or rebuild a complete `.sonar/` map for the current repository.
Use when the user wants multiple implementation strategies evaluated against the current Sonar map before coding.
This skill should be used when interpreting .sonar/ map data, querying graph.db, or working with Sonar module cards, flow narratives, and system understanding. Provides JSON schemas and SQLite query patterns.
Use when the user wants first, second, and third-order impact analysis for a proposed change using the Sonar map.
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Has parse errors
Has parse errors
Some configuration could not be fully parsed
Some configuration could not be fully parsed
Sonar is a codebase cartographer plugin for Claude Code and Codex. It builds a persistent understanding graph of any codebase and uses that map to surface relevant modules, conventions, flows, blast radius, and verification steps before agents make changes.
If you are a coding agent (Claude or similar) and the user has asked you to install Sonar: run Steps 1–3 autonomously using your Bash tool. The only step that requires the user is Step 4 (plugin reload — the shell cannot trigger a UI event).
Sonar will fail silently if Node is missing. Run:
node --version
Must be v18 or higher. If missing:
macOS: brew install node
Linux:
curl -fsSL https://deb.nodesource.com/setup_lts.x | sudo -E bash - && sudo apt-get install -y nodejs
Node on PATH: Sonar hooks run in a non-interactive shell. If Node was installed via nvm, fnm, volta, or asdf it may not be visible to hooks. Sonar auto-detects common install locations, but if hooks fail use a system-wide Node install (Homebrew, apt).
Run via Bash:
claude plugin marketplace add goldfish-1x/sonar
claude plugin install sonar
If SSH to GitHub fails, use HTTPS:
claude plugin marketplace add https://github.com/goldfish-1x/sonar
claude plugin install sonar
Run via Bash:
claude plugin list
sonar must appear in the output. If it doesn't, re-run Step 1.
Tell the user:
Sonar is installed. Please run
/reload-pluginsor restart Claude Code to activate it. Let me know when you're done and I'll run a health check.
Wait for confirmation before continuing.
Run these slash commands:
/sonar:sonar-version
Expected: version number, install path, and update status. Any error here means the plugin didn't load — check that Node is on PATH.
/sonar:sonar-status
Expected: map state for the current project. "No map" is fine on first use. Hook errors or "node not found" mean the PATH issue from Step 0 wasn't resolved.
If both return without errors, Sonar is installed and healthy.
Always orient before you code. When you receive a task, run this first:
/sonar:sonar <task description>
This gives you in seconds what would take 10-15 minutes of file exploration: which modules are involved, what conventions you must follow, what depends on what you're changing, and what tests to run. Read the briefing before reading any code.
No map yet? That's fine. Run the same command — Sonar will auto-scan the relevant modules on demand (~2-3 min) and cache the results.
Want full coverage? Run a one-time crawl:
/sonar:sonar-crawl
This takes 10-30 min depending on codebase size and builds a complete map. Commit the output to git (.sonar/modules/, .sonar/flows/, .sonar/system.json, .sonar/skeleton.json, .sonar/meta.json) so the whole team shares it.
Six hooks fire without you doing anything:
When the prompt hook injects context, read it. It's showing you something you probably haven't seen.
Task arrives
│
├─ /sonar:sonar <task> ← always start here
│
├─ Non-trivial feature?
│ YES → /sonar:sonar-explore ← 3-4 parallel strategy simulations
│
├─ Risky change?
│ YES → /sonar:sonar-impact ← 1st/2nd/3rd order cascade
│
├─ Implement
│ (hooks warn automatically)
│
├─ /sonar:sonar-verify ← convention check before pushing
│
└─ Before review?
YES → /sonar:sonar-review-context
npx claudepluginhub goldfish-1x/sonar --plugin sonarMulti-model consensus engine integrating OpenAI Codex CLI, Gemini CLI, and Claude CLI for collaborative code review and problem-solving.
Ultra-compressed communication mode. Cuts ~75% of tokens while keeping full technical accuracy by speaking like a caveman.
Comprehensive UI/UX design plugin for mobile (iOS, Android, React Native) and web applications with design systems, accessibility, and modern patterns
Curate auto-memory, promote learnings to CLAUDE.md and rules, extract proven patterns into reusable skills.
Memory compression system for Claude Code - persist context across sessions
Standalone image generation plugin using Nano Banana MCP server. Generates and edits images, icons, diagrams, patterns, and visual assets via Gemini image models. No Gemini CLI dependency required.