dev-explore

npx skills add majiayu000/claude-skill-registry --skill dev-explore-edwinhu-workflows-3 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

**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:** `.planning/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 |

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\]"