code-intelligence

Files (1)

• SKILL.md

SKILL.md (first lines)

# Code Intelligence

Use semantic tools to understand code structure, behavior, types, relationships, and diagnostics. Use plain file and text tools for filenames, comments, logs, configuration text, and exact strings

## Select evidence by question

If a Pi Lens tool you need is unavailable, call `pi_lens_activate_tools` with its name. Use the activated tool on the next model turn

- **Repository-wide orientation:** Use `project_report` when the task needs an overview of architecture, subsystems, hubs, or dependency cycles
- **Ownership and shape:**
  - `symbol_search`, then `module_report`
  - read exact bodies with `read_symbol` or `read_enclosing`
- **Types and relationships:** `lsp_navigation` for definitions, references, implementations, hover, symbols, rename previews, and call hierarchy
- **Structural patterns:** Use `ast_grep_search`. For a structural rewrite, use `ast_grep_replace` and dry-run it before applying changes. Use `ast_grep_outline` for syntax-only structure and `ast_grep_search` with `dump: true`, a representative snippet in `pattern`, and `lang` when the AST shape is unclear
- **Diagnostics:** Use `lens_diagnostics` with `source: "lsp"`, `scope: "paths"`, and explicit `paths` for focused language-server checks. Use `source: "session"` for cached findings only. Cached results do not prove unobserved files are clean

Use every evidence group that can answer a material question. Do not call a group only because it is listed. Stop when you have enough evidence to settle ownership, implementation, or correctness

## Read before editing

Before changing an identifiable function, class, method, callback, or symbol, read its actual body with `read_symbol` or `read_enclosing`. For multi-file changes, inspect relevant structure first. Use plain `read` when semantic tools are unavailable or the target is not source code

## Structural search

Use specific valid code patterns and limit them to the relevant paths. If a search finds no match, simplify it once. Use `ast_grep_search` with `dump: true`, a representative snippet in `pattern`, and `lang` when node kinds or nesting are unclear. Fall back to text search only when code structure cannot answer the question

## LSP use

Pass paths through each tool's registered `path` or `paths` parameter. When workspace symbol lookup or project resolution needs context, start from a real project file. If usage-site results can be partial, query references from the definition

From OrestesK/pi, MIT.

More from OrestesK/pi