メニュー
Codebase exploration techniques for rapid discovery, architecture analysis, pattern detection, and dependency mapping.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Systematic development workflow: Analyze → Plan → Execute → eLicit → eXamine. Use for ANY development task: features, bug fixes, refactoring, hotfixes. Triggers: "implement", "create", "build", "fix", "add feature", "refactor", "develop". Auto-detects project type (Laravel, Next.js, React, Swift) and loads framework-specific references. Enforces: files <100 lines, interfaces separated, SOLID principles, expert self-review, sniper validation. Modes: --auto (default), --manual, --skip-elicit
Auto-review skill for expert agents. After coding, expert applies elicitation techniques to self-correct before sniper validation. Inspired by BMAD-METHOD. Use when: an expert agent needs to self-review and self-correct code after the Execute phase, before sniper validation.
Use when marking a task as complete, finishing a feature, or claiming a bug is fixed. Ensures functional resolution is verified with evidence before closing. Do NOT use for: lint/type/code-quality validation (use code-quality / sniper AFTER functional verification passes).
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use when committing changes, saving work, staging and committing, or choosing a conventional commit message.
Use when committing, branching, opening PRs, or deciding merge strategy. Covers GitHub Flow (default), trunk-based, branch naming conventions, squash vs rebase, branch lifecycle, and protected branch enforcement.
Universal post-commit actions. CHANGELOG update for all repos (git tag is created POST-MERGE, not here — see `commit` command Step 8). Plugin version bumping for marketplace repos. Triggered after any code commit (except wip/amend/undo).
| name | exploration |
| description | Codebase exploration techniques for rapid discovery, architecture analysis, pattern detection, and dependency mapping. |
Runs in a forked subagent context (spawn_agent) via the explore-codebase agent. The target directory is passed as the skill argument.
Run these 5 phases in order — full commands in references/exploration-protocol.md:
main/index/server bootstrap per languagepackage.json/pyproject.toml/go.mod/Cargo.toml/composer.json| Pattern | Key Directories | Indicators |
|---|---|---|
| MVC | controllers/, models/, views/ | Rails, Laravel, Express |
| Clean Architecture | domain/, application/, infrastructure/ | DDD, Use cases |
| Hexagonal | adapters/, ports/, core/ | Ports & adapters |
| Feature-based | features/[name]/ | All layers per feature |
| Layered | presentation/, business/, data/ | Traditional 3-tier |
| Monolith | Single src/ | Mixed concerns |
| Microservices | Multiple services/ | Separate repos/folders |
| Next.js App Router | app/, components/, lib/ | Server/Client components |
| Modular Monolith | modules/[name]/ | Bounded contexts |
references/exploration-protocol.md — Load when running the 5-phase protocol (exact shell commands per phase)references/tech-stack-detection.md — Load when identifying framework/ORM/tooling per language (JS/TS, Python, Go, PHP, Rust)references/code-organization-checks.md — Load when auditing interface separation, business-logic location, or state managementreferences/response-format.md — Load when writing the final exploration reportreferences/quick-analysis-commands.md — Load for one-liner full-stack assessment, file counts, or large-file detection