cheez-search

Search repository code for symbol definitions, callers, and imports via tilth MCP.

15|1|Updated May 4, 2026
One-click install
npx skills add https://github.com/paulnsorensen/easy-cheese --skill cheez-search
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cheez-search
Source: https://github.com/paulnsorensen/easy-cheese/tree/main/skills/cheez-search
Command: npx skills add https://github.com/paulnsorensen/easy-cheese --skill cheez-search

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of locating where a symbol is defined, called, imported, or referenced across a codebase without relying on error-prone text search.

Core Features & Use Cases

  • Hard tilth MCP dependency for code search: stops immediately if the tilth MCP search tool is unavailable or unhealthy, avoiding unsafe fallbacks.
  • Definition-first semantic search: returns definitions and related usages with structure-aware context.
  • Callers and dependency-focused queries: finds call sites and module/file blast radius for refactor planning.
  • Content and regex search with guardrails: supports text-shaped queries (TODOs, errors, literals) and bounded regex within the parsed tree.

Quick Start

Ask to find a specific symbol’s definition and usages in the repository by running the tilth-backed cheez-search for that name.

Frequently Asked Questions about cheez-search

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find symbol definitions and usages across a repository using AST-aware search?

AST-aware code search locates symbol definitions and usages by parsing code structure, returning structured context for refactor planning without relying on error-prone text matching.

How do I trace call chains and find callers of a specific function in my codebase?

Tracing call chains uses dependency-focused queries to find call sites and module blast radius, mapping where a function is called and imported across the repository scope.

Can I search for TODOs and error strings within a parsed code tree instead of using plain text grep?

Content and regex search within a parsed tree supports text-shaped queries like TODOs and error strings, bounding regex scans safely within the repository scope.

Do I need the tilth MCP tool to perform AST-aware code search?

AST-aware code search strictly requires the tilth MCP search tool to be present and healthy, stopping immediately if unavailable to avoid unsafe fallbacks to host Grep or find.

What are the limitations of using AST-aware semantic search for code discovery?

AST-aware semantic search forbids falling back to host Grep, rg, find, or reading and editing whole files, stopping execution entirely if the required tilth MCP search tool is unavailable.