---
name: guaardvark-code
description: "Code intelligence over repositories Guaardvark has indexed: semantic code search, exact-text search, file listing, PageRank repository map, import dependency graph, reading one class or function, analysis and generated rewrites, plus the System Mapper and self-improvement status. Use when the user asks where something is implemented, how modules depend on each other, or wants an architecture map of an indexed repo."
license: "MIT"
metadata:
  decimalai-skill-id: "910d0e15-d9e8-435c-9863-2faa814b4127"
  decimalai-version-id: "56519f1f-aaee-4661-8606-2845a11f5608"
  decimalai-version: "3"
  decimalai-body-sha256: "e4f571c4ad1481e13a50374618a0a35901710873fff614a617eea812699c4f8b"
  decimalai-name: "guaardvark/code"
  decimalai-format: "1"
  decimalai-invocation: "model"
  decimalai-category: "coding"
  decimalai-source: "https://app.decimal.ai/s/guaardvark-code@3/SKILL.md"
---
# Code intelligence with Guaardvark (MCP tools)

| tool | use |
|---|---|
| `list_code_repositories` | which folders are marked as repositories (gives the folder id) |
| `search_codebase` | search Guaardvark's own source: by meaning once a code search index is built (System Map page), otherwise by words and names |
| `search_code` | case-insensitive regex across files |
| `list_code_files` | directory listing to orient |
| `read_code` | a file, or a line range of it (`start_line`, `end_line`); large files come back in pages |
| `read_ast_node` | one class or function by name from a Python file |
| `get_repository_map` | PageRank-ranked architectural map for a folder id |
| `get_dependency_graph` | file-level import graph for a folder id |
| `analyze_code` | structure, patterns, improvement notes for a file |
| `codegen` | a complete modified version of a file from instructions (writes a new file) |
| `verify_change` | confirm text now exists in a file after an edit |
| `map_codebase` | run the System Mapper: the most severe findings, then the numbers |
| `system_map_query` | ask the System Mapper about Guaardvark's code: `where <feature>`, `module <path>`, `symbol <name>` (callers, callees), `route <path>`, `tool <name>`, `subsystem <name>`, `impact <path>` (dependents, tests to run), `findings <scope>` |
| `self_improvement_status` | can the self-improvement engine run (lock, flag, already running) |
| `swarm_status` | the coding swarm (see the swarm skill) |

## Pattern

1. `list_code_repositories` → folder id.
2. `get_repository_map` for the shape, `search_codebase` for the question.
3. Read the exact code (`read_code` / `read_ast_node`) before answering; quote file and line.
4. Edits: make them with your own editor tools in the user's checkout; `verify_change` afterwards.

## Rules

- These tools read Guaardvark's index, which can lag the working tree; when it matters, read the
  file from disk too.
- `map_codebase`, `system_map_query` and `self_improvement_status` are read-only here. Dispatching a fix to the
  self-improvement engine is done in the Studio, on purpose.