tree-sitter-analyzer

Analyze Julia modules and extract dependencies using Tree-Sitter incremental parsing.

60|13|Updated Dec 22, 2025
One-click install
npx skills add https://github.com/plurigrid/asi --skill tree-sitter-analyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tree-sitter-analyzer
Source: https://github.com/plurigrid/asi/tree/main/ies/music-topos/.codex/skills/tree-sitter-analyzer
Command: npx skills add https://github.com/plurigrid/asi --skill tree-sitter-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated code structure analysis for module verification and cross-prover theorem mapping using tree-sitter incremental parsing to drastically speed up analysis.

Core Features & Use Cases

  • Module analysis and symbol extraction
  • Dependency graph construction
  • Integration point discovery and circular dependency detection

Quick Start

Use analyze_module(path) to inspect a Julia module and build a dependency graph for a project.

Frequently Asked Questions about tree-sitter-analyzer

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

FAQPage Schema
How do I analyze Julia module dependencies and build a dependency graph?

Module dependency analysis extracts symbols, imports, and exports from Julia code using tree-sitter incremental parsing to construct a complete dependency graph. Use analyze_module(path) to inspect a module and automatically map cross-module relationships across your project.

Can tree-sitter detect circular dependencies in Julia code?

Yes. Tree-sitter-based analysis identifies circular dependencies by tracing module imports and exports across your codebase. The dependency graph construction returns integration reports that flag circular references, enabling early detection in large ecosystems.

What makes tree-sitter faster than traditional AST parsing for code analysis?

Tree-sitter uses incremental parsing, updating only changed portions of the syntax tree instead of reparsing entire files. This approach delivers sub-millisecond operation times, making it practical for analyzing hundreds to thousands of modules in real time.

How do I extract function signatures and struct definitions from Julia modules?

Tree-sitter parsing automatically extracts structured artifacts including FunctionSignature, StructDefinition, MacroUsage, and DocstringInfo from your Julia code. These outputs enable symbol-level verification and cross-module integration point discovery.

Does this work for large software ecosystems with many interdependent modules?

Yes. The Skill handles hundreds to thousands of modules efficiently with zero external dependencies and sub-millisecond performance. It's designed for cross-module verification scenarios and supports integration verification across complex ecosystems.

Why use code structure analysis instead of static imports alone?

Structure analysis via tree-sitter goes beyond import statements to extract symbol usage, macro invocations, and actual integration points. This enables circular-dependency detection and verification scenarios that import inspection alone cannot surface.