Menú
Explore a codebase or directory to understand its structure and purpose
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Guided git commit workflow — review changes, draft message, stage, commit
Manage context pressure during large codebase work without losing critical state.
Create a pull request with structured summary and test plan
Interactive debugging — reproduce, isolate, trace, fix
Implement a requested code change end-to-end with scoped edits and verification.
Investigate production-like failures from symptoms, logs, and reproduction steps.
| name | explore |
| description | Explore a codebase or directory to understand its structure and purpose |
| when_to_use | When entering an unfamiliar project, directory, or module |
| required_tools | ["bash","symbol_index","imports"] |
| tags | ["exploration","understanding"] |
| activation | {"input_patterns":["(?i)(explore|what.*is.*this|show.*structure|项目结构|看看)"]} |
${ARGS}
Use CLI commands (find, git ls-files, tree when available) to map top-level structure. Count files by type. Identify the organizational pattern: flat, layered, feature-based, monorepo.
Find and read: manifest files (Cargo.toml, package.json, pyproject.toml, go.mod), README, CONTRIBUTING, architecture docs, main entry point. Map the dependency graph: what depends on what, are there layers, are there circular references.
Use grep/rg and symbol tools to find recurring patterns: error handling style, testing approach, configuration management, naming conventions. Identifying conventions early accelerates all subsequent work.
Purpose (one sentence) · Stack (language, framework, dependencies) · Structure (directory layout with role of each unit) · Entry points · Conventions · Key files (3-5 highest information-density files).
