What is the Iron Law of Exploration?

It is a strict requirement that the AI must read 5-10 identified key files in their entirety to prevent implementation errors based on incomplete architectural assumptions.

Which search tools does dev-explore utilize?

It prioritizes semantic search using ast-grep (sg) for AST-based pattern matching and ripgrep-all (rga) for searching through non-code files.

Does this skill support parallel processing?

Yes, it launches 3-5 background agents simultaneously to explore different areas of the code (tests, features, architecture) without blocking the main chat.

How does it handle test discovery?

The skill treats test infrastructure as a 'Gate.' If it cannot find a way to execute and verify code (via pytest, jest, etc.), it halts the workflow to propose adding tests first.

When should I use the dev-explore skill?

Use dev-explore as Phase 2 of your workflow, immediately after brainstorming requirements but before writing any code, to ensure you understand where logic lives and how it works.

Codebase Explorer (dev-explore)

Name: Codebase Explorer (dev-explore)
Author: edwinhu

byedwinhu

Developer Tools

Maps codebase architecture and discovers implementation patterns using parallel background agents and semantic search.

About

dev-explore is a specialized exploration tool designed for the critical second phase of the software development lifecycle. It automates the complex task of understanding unfamiliar repositories by launching parallel agents to trace execution paths, map architectural layers, and identify existing code patterns. Unique to this skill is the 'Iron Law of Exploration,' which ensures the AI physically reads prioritized files rather than guessing their contents. By mandating test infrastructure discovery as a prerequisite for implementation, dev-explore prevents technical debt and ensures every new feature is built upon a foundation of verifiable code.

Key Features

Direct integration with sequential /dev workflows for seamless transitions
Mandatory test infrastructure 'Gate' to enforce TDD best practices
Automated prioritized key file list generation and consolidation
Parallel background agent execution for multi-threaded repository analysis
0 GitHub stars
Semantic pattern matching via ast-grep to identify code conventions

Use Cases

Onboarding onto a complex legacy codebase to map dependencies and architecture
Locating existing feature patterns to ensure implementation consistency
Verifying and documenting test frameworks before starting new feature development

About

Key Features

Direct integration with sequential /dev workflows for seamless transitions
Mandatory test infrastructure 'Gate' to enforce TDD best practices
Automated prioritized key file list generation and consolidation
Parallel background agent execution for multi-threaded repository analysis
0 GitHub stars
Semantic pattern matching via ast-grep to identify code conventions

Use Cases

Onboarding onto a complex legacy codebase to map dependencies and architecture
Locating existing feature patterns to ensure implementation consistency
Verifying and documenting test frameworks before starting new feature development