coderlm

Explore codebases structurally and navigate symbols across multiple programming languages.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/arthrod/conejo-skills --skill coderlm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coderlm
Source: https://github.com/arthrod/conejo-skills/tree/main/skills/coderlm
Command: npx skills add https://github.com/arthrod/conejo-skills --skill coderlm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill solves the inefficiency of traditional codebase navigation by replacing imprecise grep-based searching with a structural, tree-sitter-backed index that understands symbols, call chains, and execution paths.

Core Features & Use Cases

  • Structural Navigation: Find exact function implementations, variable definitions, and call sites without loading entire files into context.
  • Causal Tracing: Trace execution paths from entrypoints to outcomes by querying callers and test references.
  • Use Case: When debugging a complex bug, use this skill to identify every function that calls a specific API endpoint, retrieve only the relevant function bodies, and verify test coverage for those specific symbols.

Quick Start

Initialize a new session for the current project and search for the definition of the main entrypoint function.

Frequently Asked Questions about coderlm

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

FAQPage Schema
How do I find function implementations and call sites in a large codebase without loading entire files?

Structural codebase navigation using a tree-sitter-backed index server retrieves exact function implementations and call sites without loading entire files into context. It maps symbol relationships to provide precise retrieval across large repositories.

What is the best way to trace execution paths from entrypoints to outcomes for debugging?

Causal tracing maps execution paths from entrypoints to outcomes by querying callers and test references. This approach identifies every function calling a specific endpoint and verifies test coverage for targeted symbols during complex bug debugging.

Does tree-sitter structural navigation work for multiple programming languages?

Yes, tree-sitter structural navigation supports multiple programming languages by maintaining a symbol-aware index. It enables precise retrieval of variable definitions, function implementations, and test references across diverse codebases.

How do I initialize a session to search for the main entrypoint function definition?

Initialize a new session for the current project to search for the definition of the main entrypoint function. The tree-sitter index server then allows structural queries to locate specific symbols and their implementations.

Why should I use structural codebase exploration instead of grep-based searching?

Structural codebase exploration replaces imprecise grep-based searching with a tree-sitter-backed index that understands symbols, call chains, and execution paths. This provides exact function implementations and variable definitions without loading entire files into context.

Can I retrieve only the relevant function bodies when debugging a complex bug?

Yes, structural codebase exploration retrieves only the relevant function bodies by querying the tree-sitter index for specific symbols. This allows you to identify callers, trace execution paths, and verify test coverage for those exact functions.