Verified:GitHub

dev-explore

Map codebase architecture and trace execution paths with semantic search tools.

19|5|Updated Jan 4, 2026

Search Tags:#semantic search #codebase analysis #code exploration #test infrastructure #feature discovery #architecture mapping

Ready to run

npx skills add https://github.com/edwinhu/workflows --skill dev-explore-edwinhu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-explore
Source: https://github.com/edwinhu/workflows/tree/main/lib/skills/dev-explore
Command: npx skills add https://github.com/edwinhu/workflows --skill dev-explore-edwinhu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you understand the structure, components, and execution flow of a codebase, enabling you to efficiently locate relevant files and grasp architectural patterns.

Core Features & Use Cases

Codebase Mapping: Visualize the architecture, layers, and dependencies within a project.
Feature Discovery: Identify similar features and trace execution paths from entry points to data storage.
Test Infrastructure Identification: Locate testing frameworks, patterns, and tools used in the project.
Use Case: When starting a new project or feature, use this Skill to quickly get an overview of the existing code structure, understand how different modules interact, and find where to begin implementing new functionality.

Quick Start

Use the dev-explore skill to map the architecture of the current codebase.

Frequently Asked Questions about dev-explore

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

FAQPage Schema

How do I map my codebase architecture and trace execution paths?▼

To map codebase architecture and trace execution paths, you can use semantic code search tools like ast-grep and ripgrep-all to analyze code and non-code files, identifying key files, architectural layers, and project components.

What is the best way to locate test infrastructure and frameworks in a project?▼

Locating test infrastructure involves using semantic code search to discover testing frameworks, patterns, and tools used in the project, ensuring comprehensive discovery of test components and patterns across the codebase.

How do I identify similar features and trace execution paths from entry points to data storage?▼

Identifying similar features and tracing execution paths from entry points to data storage requires exploring the codebase architecture to understand how different modules interact and locate relevant files.

Can I use semantic code search to analyze both code and non-code files for feature discovery?▼

Yes, semantic code search tools like ast-grep and ripgrep-all analyze both code and non-code files, ensuring comprehensive discovery of project components, patterns, and similar features during codebase exploration.

Does this codebase analysis approach work for understanding architectural layers and dependencies?▼

Yes, codebase analysis using semantic search tools visualizes the architecture, layers, and dependencies within a project, helping you grasp architectural patterns and understand software structure efficiently.

When should I use semantic code search for codebase exploration instead of manual browsing?▼

Use semantic code search for codebase exploration when starting a new project or feature, to quickly get an overview of existing code structure, understand module interactions, and find where to begin implementing functionality.