메뉴
Analyze implementation details, trace data flow, explain technical workings, locate files, and consolidate codebases. Use when you need to understand HOW code works, find file locations, or assess technical debt.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Checkpoint episodes and create handoff packs for multi-agent session continuity
Configure, test, benchmark, and manage embedding providers for semantic search and vector operations
Create and traverse typed relationships between episodes for dependency tracking and knowledge graphs
Manage episode tags for organization, filtering, and retrieval across the memory system
Generate task playbooks and explain patterns using learned strategies from episodic memory
Record and analyze recommendation sessions and feedback to drive the self-learning loop
| name | codebase-analyzer |
| description | Analyze implementation details, trace data flow, explain technical workings, locate files, and consolidate codebases. Use when you need to understand HOW code works, find file locations, or assess technical debt. |
Analyze implementation details, trace data flow, explain technical workings, and locate files.
| Mode | Purpose | Output |
|---|---|---|
| Locator | Find file locations | File paths with descriptions |
| Analyzer | Trace implementation | Data flow with file:line refs |
| Consolidator | Assess debt/refactor | Debt report + recommendations |
| Pattern | Purpose |
|---|---|
*service*, *handler* | Business logic |
*test*, *spec* | Test files |
*.config.* | Configuration |
Rust: src/, crates/ | Source files |
## File Locations for [Feature]
### Implementation Files
- `src/services/feature.rs` - Main service logic
### Test Files
- `src/services/__tests__/feature.test.rs`
### Configuration
- `config/feature.json`
✓ Include file:line references ✓ Read files thoroughly before explaining ✓ Trace actual code paths ✓ Group files logically by purpose ✓ Use multiple search patterns
✗ Guess about implementation ✗ Skip error handling ✗ Make architectural recommendations without context ✗ Analyze without clear goals
You are a documentarian. Map and explain, don't redesign.