Use bonsai-ninja as compiler-backed structural evidence when mapping a codebase, finding symbols, tracing behavior, inspecting dataflow, debugging across files, reviewing change impact, exporting graph facts, or running SAST.
Use before searching, reading, or editing files in this repo (or any repo with a "calm" MCP server), or whenever unsure which CALM tool fits — a self-triggerable orientation to the CALM Stage 1-8 tool workflow (repooverview → locate → source → callers → editcontext → editsymbol/editlines → diffimpact →…
Use when navigating code, understanding unfamiliar functions, finding definitions or references, tracing call hierarchies, preparing for refactoring, or analyzing code impact. Enforces LSP-first semantic code intelligence with mandatory pre-edit checks, impact analysis before refactoring, and post-edit diagnostics.…
Navigates the local RepoSkein Code Property Graph to understand repository architecture. Use whenever modifying code, tracing dependencies, assessing change impact, or summarizing functions in a repo containing .reposkein/.
Installs and verifies RepoSkein (the deterministic code-graph MCP server) in the current repository. Use when an agent wants RepoSkein's structural navigation but the tools are missing, error with "REPOSKEINREPOPATH", or the repo has no .reposkein/ directory — i.e. set RepoSkein up and confirm it runs.
Orchestrate multi-agent workflows through RagCode. Turn a natural-language collaboration pattern (e.g. "Gemini plans, Claude breaks down, Codex implements, Claude reviews") into a validated DAG workflow spec, then run it with the RagCode agent workflow engine. Trigger when the user asks to coordinate multiple AI…
Manage shared cross-AI memories for this project through RagCode MCP tools (memorywrite, memoryquery, memorylist, memorydelete), with ragcode memory CLI fallback when MCP is unavailable. Read prior decisions, user preferences, and feedback written by other AI agents, and record new insights so they persist across…
Read-only review of a non-empty comment delta. Flags narration with evidence, names what it deliberately kept, and reports removed rationale. Use when the user asks to check comments or a finished diff's pre-gate found added, modified, or deleted comments; skip automatic routing when no comment changed.
Read-only review of whether the tests in a finished change actually prove its behaviour — changed code no test reaches, a test exercising a different path than the one that changed, an assertion edited to match the new output, and a suite that ran nothing. Use after implementation, and whenever a change claims to be…
Choose the lightest Mastermind workflow that fits the risk, then create an evidence-grounded verified or strict task contract for delegated implementation. Direct work deliberately uses no task spec.
How a new language enters Kivgraph's graph - the two routes and why one of them is almost always wrong, the four decisions that cannot be migrated later, the branches that decide what your language is without asking, and the gates that fail closed. Use when adding or extending language support, when touching…
Cómo y sobre todo cuándo se publica una release de Kivgraph - la versión sólo sube, los tres sitios donde vive, qué verifica CI, y la lista de cambios que NO merecen release. Usar al proponer o preparar una release, al tocar internal/version/version.go, al crear un tag vX.Y.Z, o cuando alguien pida "saca una versión".
Cómo se ejecutan y se escriben los tests de Kivgraph - las tres suites, el tag ladybug que no se invoca a mano, qué se salta y por qué, y el smoke test del binario. Usar al correr tests, al añadirlos, ante un fallo de enlazado library 'lbug' not found, ante un SKIP inesperado, o antes de cerrar una tarea.
Audit a PR's structural choices against architecture-priming, the repo's own architecture.md, and any nested boundary configs. Use when the user says "audit this PR's architecture", "check the boundaries", "is this PR clean structurally", "post-merge review of.
Voice, tone, and format for the public Codemap docs (apps/docs, built with Blume). Use when authoring or editing apps/docs prose — landing, guides, concepts, recipes, reference, generated API — or deciding headline grammar, benefit framing, peer framing, or anti-pitch wording.
Find deepening opportunities in the codebase, informed by the domain language in docs/glossary.md and the architecture in docs/architecture.md. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
Use this skill to answer codebase architecture questions, trace dependencies, find callers/callees, calculate blast radius, and explore the code graph. ACTIVATE when the user asks "how does X work", "what handles Y", "where is Z defined", "explain the mechanism", "who calls", "blast radius", "shortest path", "trace…
Compiler-exact code search for .NET solutions - find where a symbol is defined, every reference to it, who calls it, and what a change would break. Covers C#, VB, Razor Pages, MVC views and Blazor components, which grep and every other code-intelligence tool miss. Deterministic, built on Roslyn, never modifies the…
Gather focused local repository context with ivygrep before implementing, debugging, reviewing, or explaining code. Use for coding tasks involving unfamiliar paths, branch changes, stack traces, architectural relationships, callers, dependents, tests, configuration, or documentation. Prefer one bounded context pack…
Use this skill when modifying AI agents, skills, prompts, commands, hooks, instructions, MCP configuration, or platform-specific AI customization files.
Use the Cerebro brain to understand a codebase cheaply instead of re-reading folders. Invoke when starting work on a project, when you need to understand what a file does or where something lives, or before exploring directories. Query cerebromap / cerebroget / cerebrosearch first; record what you learn with…