Systematically populate the Brain knowledge base using Serena's LSP-powered symbol analysis for accurate, comprehensive codebase understanding.
Transform an undocumented codebase into a rich, searchable knowledge repository using Serena's LSP-powered symbol analysis.
| Trigger Phrase | Operation |
|---|---|
encode this repository | Full 12-phase encoding pipeline |
populate brain with this codebase | Full encoding pipeline |
onboard to this repo | Discovery + foundation phases |
refresh project understanding | Re-run encoding on updated codebase |
build knowledge base for this project | Full encoding pipeline |
Use this skill when:
Use research-and-incorporate instead when:
/repo-encoder
/repo-encoder ./my-project
"encode this repository"
"populate brain with this codebase"
| Input | Output | Duration |
|---|---|---|
| Codebase path | Brain memory notes + docs | 30-60 min |
claude plugins list | grep serenamcp__plugin____brain__search({ "query": "test" })Assess project size, complexity, and structure. Produce a structure map.
Create 5-10 project overview Brain memory notes covering purpose, tech stack, and entry points.
Create 1-3 dependency notes documenting external libraries and internal references.
Use Serena find_symbol and find_referencing_symbols to produce 10-15 architecture notes.
Create component Brain memory notes with relations. Deduplicate before creating.
Document 8-12 recurring code patterns, conventions, and idioms.
Create 1-2 notes per critical feature describing behavior and implementation.
Record design decisions with rationale and alternatives considered.
Store code artifacts (configs, schemas, key files) as Brain memory notes.
Create a symbol index note for navigation.
Produce long-form documentation summarizing the codebase.
Create an architecture reference note linking all prior phases.
See references/phases.md for full phase details.
0 -> 1 -> 1B -> 2 -> 2B -> 3 -> 4 -> 5 -> 6 -> 6B -> 7 -> 7B
Guidelines:
find_symbol and find_referencing_symbols| Profile | Total Notes | Documents | Entities |
|---|---|---|---|
| Small Simple | 17-31 | 2 | 3-5 |
| Small Complex | 28-46 | 2 | 5-10 |
| Medium | 38-66 | 2-3 | 10-20 |
| Large | 66-112 | 3-6 | 20-40 |
| Principle | Description |
|---|---|
| Symbol-accurate | Use LSP data, not guesses |
| Atomic | One concept per note |
| Size | 200-400 words ideal |
| Linking | Connect related notes via relations |
After encoding, verify all outputs meet quality standards:
See references/validation.md for test commands.
| Avoid | Why | Instead |
|---|---|---|
| Skipping Phase 0 discovery | Wastes effort on wrong project scope | Always assess project size and complexity first |
| Creating non-atomic notes | Pollutes search results, hard to maintain | One concept per note, 200-400 words |
| Duplicate notes | Bloats knowledge graph, inconsistent links | Deduplicate notes before creating |
| Skipping validation | No confidence in encoding quality | Run validation checklist after completion |
| Document | Content |
|---|---|
| phases.md | Detailed phase workflows |
| templates.md | Note templates |
| validation.md | Validation test commands |
/code-symbols - Serena symbol analysis/code-architecture - Architectural analysis with Brain memory