smart-explore

Locates and outlines code symbols using tree-sitter AST parsing across the whole project.

1|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/dwaynimay/IoTProject --skill smart-explore-dwaynimay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smart-explore
Source: https://github.com/dwaynimay/IoTProject/tree/main/.agents/skills/smart-explore
Command: npx skills add https://github.com/dwaynimay/IoTProject --skill smart-explore-dwaynimay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates slow, guess-and-check code reading by finding the right functions, classes, and structural sections across a repository before you load full file contents.

Core Features & Use Cases

  • Structural discovery with AST parsing: Finds ranked symbols and signatures across a codebase so you can understand where things live.
  • Token-efficient exploration workflow: Uses search for a code map, outline for file structure, and unfold for targeted implementations.
  • Primary tool switch for code navigation: Encourages smart_search/smart_outline/smart_unfold instead of Read/Grep/Glob for code files.

Quick Start

Use smart_search to locate a concept in the firmware server codebase, then unfold only the most relevant symbol to inspect its implementation.

Frequently Asked Questions about smart-explore

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

FAQPage Schema
How do I search code structure using AST parsing to find functions across a repository?

Search code structure across a repository using AST parsing by requesting ranked symbols and signatures to locate functions and classes before loading full file contents. This structural discovery maps where code elements live without guess-and-check reading.

What is the best way to optimize tokens when navigating and reading large code files?

Optimize tokens when navigating large code files by using a three-step workflow: search for a code map, outline the file skeleton, and unfold only the targeted symbol implementation. This avoids full-file reads and saves token usage.

Can I use tree-sitter AST parsing for symbol discovery across multiple programming languages?

Yes, tree-sitter AST parsing supports repository-wide symbol discovery across supported programming languages. It finds structural sections, functions, and classes to provide efficient navigation and targeted review across different codebases.

How do I extract a file skeleton or structural outline without reading the entire code file?

Extract a file skeleton by requesting a structural outline of the code file. AST parsing generates this skeleton by identifying code elements and structural sections, allowing you to understand the file architecture without loading the full content.

Does structural code search work better than standard text search for code navigation?

Structural code search works better than standard text search for code navigation because it uses tree-sitter AST parsing to find ranked symbols and structural sections. This targets code elements directly instead of matching arbitrary text strings.

When should I avoid reading full file contents during code exploration?

Avoid reading full file contents during code exploration when you need to locate specific functions or classes in a large repository. Use structural search and symbol unfolding instead to inspect only relevant implementations and reduce token consumption.