dev-explore
REQUIRED Phase 2 of /dev workflow after dev-brainstorm. This skill should be used when the user asks to 'explore the codebase', 'map architecture', 'find similar features', 'discover test infrastructure', 'trace execution paths', 'identify code patterns', or needs to understand WHERE code lives and HOW it works before implementation. Launches parallel explore agents and returns prioritized key files list.
npx skills add majiayu000/claude-skill-registry --skill dev-explore --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
**Announce:** "I'm using dev-explore (Phase 2) to map the codebase." ## Contents - [The Iron Law of Exploration](#the-iron-law-of-exploration) - [What Explore Does](#what-explore-does) - [Process](#process) - [Test Infrastructure Discovery](#test-infrastructure-discovery) - [Key Files List Format](#key-files-list-format) - [Red Flags](#red-flags---stop-if-youre-about-to) - [Output](#output) # Codebase Exploration Map relevant code, trace execution paths, and return prioritized files for reading. **Prerequisite:** `.claude/SPEC.md` must exist with draft requirements. <EXTREMELY-IMPORTANT> ## The Iron Law of Exploration **RETURN KEY FILES LIST. This is not negotiable.** Every exploration, you MUST return: 1. Summary of findings 2. **5-10 key files** with line numbers and purpose 3. Patterns discovered After agents return, **you MUST read all key files** before proceeding. **STOP if you're about to move on without reading all key files.** </EXTREMELY-IMPORTANT> ### Rationalization Table - STOP If Thinking: | Excuse | Reality | Do Instead | |--------|---------|------------| | "I can design without reading all key files" | You'll miss critical patterns | READ every file on the list | |
- Contents
- The Iron Law of Exploration
- Rationalization Table - STOP If Thinking:
- Honesty Framing
- No Pause After Completion
- What Explore Does
- Process
- 1. Launch 3-5 Explore Agents in Parallel + Background
- 1b. Collect Background Results
- 2. Consolidate Key Files
- 3. Read All Key Files
- 4. Document Findings
- Code Search Tools
- Test Infrastructure Discovery
Find test directories across common locations ls -d tests/ test/ spec/ __tests__/ 2>/dev/null Find test frameworks in build configuration cat meson.build 2>/dev/null | grep -i test Find test frameworks in Node package manifest cat package.json 2>/dev/null | grep -E "(test|jest|mocha|vitest)" Find pytest configuration in Python projects cat pyproject.toml 2>/dev/null | grep -i pytest Find dev dependencies in Rust projects cat Cargo.toml 2>/dev/null | grep -i "\[dev-dependencies\]"
What does the dev-explore skill do?
REQUIRED Phase 2 of /dev workflow after dev-brainstorm. This skill should be used when the user asks to 'explore the codebase', 'map architecture', 'find similar features', 'discover test infrastructure', 'trace execution paths', 'identify code patterns', or needs to understand WHERE code lives and HOW it works before implementation. Launches parallel explore agents and returns prioritized key files list.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill dev-explore --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.