[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CD2AKDM9Y3X0KWFRK8SJXY":3,"skill-same:01M6CD2AKDM9Y3X0KWFRK8SJXY":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":26,"linkOnly":27,"markdownContent":28,"markdownBody":29,"frontMatter":30,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":14,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":42,"install":43,"resources":56},"01M6CD2AKDM9Y3X0KWFRK8SJXY","repo-encoder",null,"Systematically populate the Brain knowledge base using Serena's LSP-powered symbol analysis for accurate, comprehensive codebase understanding.","loriensleafs\u002Fbrain","loriensleafs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F315385?v=4","01M6CCYZETMCJPTHNS258YRCBC","Peter Kloss","01M6CCYZK25T8516A39S9PCJT7",0,"MIT","https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Frepo-encoder\u002FSKILL.md",[],[19,20,21,22,23,24,25],"repo","repo encoder","directory","analysis","architect","knowledge","default","2026-11-10 10:12:30",false,"---\nname: repo-encoder\ndescription: Systematically populate the Brain knowledge base using Serena's LSP-powered\n  symbol analysis for accurate, comprehensive codebase understanding.\nlicense: MIT\nmodel: claude-sonnet-4-5\nmetadata:\n  version: 1.1.0\n  argument-hint: 'Project path or name to encode (default: current directory)'\nagents: [analyst, architect]\n---\n\n# Encode Repository\n\nTransform an undocumented codebase into a rich, searchable knowledge repository using Serena's LSP-powered symbol analysis.\n\n## Triggers\n\n| Trigger Phrase | Operation |\n|----------------|-----------|\n| `encode this repository` | Full 12-phase encoding pipeline |\n| `populate brain with this codebase` | Full encoding pipeline |\n| `onboard to this repo` | Discovery + foundation phases |\n| `refresh project understanding` | Re-run encoding on updated codebase |\n| `build knowledge base for this project` | Full encoding pipeline |\n\n## When to Use\n\nUse this skill when:\n\n- Onboarding to a new repository that lacks Brain memory notes\n- Repository structure has changed significantly since last encoding\n- Brain searches return sparse or outdated results for the project\n\nUse `research-and-incorporate` instead when:\n\n- Researching an external topic, not encoding a codebase\n- You need analysis of a single concept, not full repository encoding\n\n## Quick Start\n\n```text\n\u002Frepo-encoder\n\u002Frepo-encoder .\u002Fmy-project\n\"encode this repository\"\n\"populate brain with this codebase\"\n```\n\n| Input | Output | Duration |\n|-------|--------|----------|\n| Codebase path | Brain memory notes + docs | 30-60 min |\n\n## Prerequisites\n\n1. **Serena plugin**: `claude plugins list | grep serena`\n2. **Brain MCP**: Test with `mcp__plugin____brain__search({ \"query\": \"test\" })`\n3. If missing, set up Brain MCP first\n\n## Process\n\n### Phase 0: Discovery\n\nAssess project size, complexity, and structure. Produce a structure map.\n\n### Phase 1: Foundation\n\nCreate 5-10 project overview Brain memory notes covering purpose, tech stack, and entry points.\n\n### Phase 1B: Dependencies\n\nCreate 1-3 dependency notes documenting external libraries and internal references.\n\n### Phase 2: Symbols\n\nUse Serena `find_symbol` and `find_referencing_symbols` to produce 10-15 architecture notes.\n\n### Phase 2B: Entities\n\nCreate component Brain memory notes with relations. Deduplicate before creating.\n\n### Phase 3: Patterns\n\nDocument 8-12 recurring code patterns, conventions, and idioms.\n\n### Phase 4: Features\n\nCreate 1-2 notes per critical feature describing behavior and implementation.\n\n### Phase 5: Decisions\n\nRecord design decisions with rationale and alternatives considered.\n\n### Phase 6: Artifacts\n\nStore code artifacts (configs, schemas, key files) as Brain memory notes.\n\n### Phase 6B: Symbol Index\n\nCreate a symbol index note for navigation.\n\n### Phase 7: Documents\n\nProduce long-form documentation summarizing the codebase.\n\n### Phase 7B: Architecture\n\nCreate an architecture reference note linking all prior phases.\n\nSee [references\u002Fphases.md](references\u002Fphases.md) for full phase details.\n\n## Execution Order\n\n```text\n0 -> 1 -> 1B -> 2 -> 2B -> 3 -> 4 -> 5 -> 6 -> 6B -> 7 -> 7B\n```\n\n**Guidelines**:\n\n- Execute phases in order\n- Use Serena's `find_symbol` and `find_referencing_symbols`\n- Deduplicate notes before creating\n- Link notes via relations bidirectionally\n- Create summary notes for large documents\n\n## Memory Targets\n\n| Profile | Total Notes | Documents | Entities |\n|---------|-------------|-----------|----------|\n| Small Simple | 17-31 | 2 | 3-5 |\n| Small Complex | 28-46 | 2 | 5-10 |\n| Medium | 38-66 | 2-3 | 10-20 |\n| Large | 66-112 | 3-6 | 20-40 |\n\n## Quality Principles\n\n| Principle | Description |\n|-----------|-------------|\n| Symbol-accurate | Use LSP data, not guesses |\n| Atomic | One concept per note |\n| Size | 200-400 words ideal |\n| Linking | Connect related notes via relations |\n\n## Validation\n\nAfter encoding, verify all outputs meet quality standards:\n\n- [ ] Test search: \"How do I add a new API endpoint?\"\n- [ ] Test dependency query: \"What dependencies does this project use?\"\n- [ ] List notes by folder\n- [ ] Verify note relations\n- [ ] Check Symbol Index note exists\n- [ ] Check Architecture Reference note exists\n- [ ] All target components have Brain memory notes\n- [ ] Notes linked via relations\n- [ ] No duplicate notes in knowledge graph\n\nSee [references\u002Fvalidation.md](references\u002Fvalidation.md) for test commands.\n\n## Anti-Patterns\n\n| Avoid | Why | Instead |\n|-------|-----|---------|\n| Skipping Phase 0 discovery | Wastes effort on wrong project scope | Always assess project size and complexity first |\n| Creating non-atomic notes | Pollutes search results, hard to maintain | One concept per note, 200-400 words |\n| Duplicate notes | Bloats knowledge graph, inconsistent links | Deduplicate notes before creating |\n| Skipping validation | No confidence in encoding quality | Run validation checklist after completion |\n\n## References\n\n| Document | Content |\n|----------|---------|\n| [phases.md](references\u002Fphases.md) | Detailed phase workflows |\n| [templates.md](references\u002Ftemplates.md) | Note templates |\n| [validation.md](references\u002Fvalidation.md) | Validation test commands |\n\n## Related Skills\n\n- `\u002Fcode-symbols` - Serena symbol analysis\n- `\u002Fcode-architecture` - Architectural analysis with Brain memory\n","# Encode Repository\n\nTransform an undocumented codebase into a rich, searchable knowledge repository using Serena's LSP-powered symbol analysis.\n\n## Triggers\n\n| Trigger Phrase | Operation |\n|----------------|-----------|\n| `encode this repository` | Full 12-phase encoding pipeline |\n| `populate brain with this codebase` | Full encoding pipeline |\n| `onboard to this repo` | Discovery + foundation phases |\n| `refresh project understanding` | Re-run encoding on updated codebase |\n| `build knowledge base for this project` | Full encoding pipeline |\n\n## When to Use\n\nUse this skill when:\n\n- Onboarding to a new repository that lacks Brain memory notes\n- Repository structure has changed significantly since last encoding\n- Brain searches return sparse or outdated results for the project\n\nUse `research-and-incorporate` instead when:\n\n- Researching an external topic, not encoding a codebase\n- You need analysis of a single concept, not full repository encoding\n\n## Quick Start\n\n```text\n\u002Frepo-encoder\n\u002Frepo-encoder .\u002Fmy-project\n\"encode this repository\"\n\"populate brain with this codebase\"\n```\n\n| Input | Output | Duration |\n|-------|--------|----------|\n| Codebase path | Brain memory notes + docs | 30-60 min |\n\n## Prerequisites\n\n1. **Serena plugin**: `claude plugins list | grep serena`\n2. **Brain MCP**: Test with `mcp__plugin____brain__search({ \"query\": \"test\" })`\n3. If missing, set up Brain MCP first\n\n## Process\n\n### Phase 0: Discovery\n\nAssess project size, complexity, and structure. Produce a structure map.\n\n### Phase 1: Foundation\n\nCreate 5-10 project overview Brain memory notes covering purpose, tech stack, and entry points.\n\n### Phase 1B: Dependencies\n\nCreate 1-3 dependency notes documenting external libraries and internal references.\n\n### Phase 2: Symbols\n\nUse Serena `find_symbol` and `find_referencing_symbols` to produce 10-15 architecture notes.\n\n### Phase 2B: Entities\n\nCreate component Brain memory notes with relations. Deduplicate before creating.\n\n### Phase 3: Patterns\n\nDocument 8-12 recurring code patterns, conventions, and idioms.\n\n### Phase 4: Features\n\nCreate 1-2 notes per critical feature describing behavior and implementation.\n\n### Phase 5: Decisions\n\nRecord design decisions with rationale and alternatives considered.\n\n### Phase 6: Artifacts\n\nStore code artifacts (configs, schemas, key files) as Brain memory notes.\n\n### Phase 6B: Symbol Index\n\nCreate a symbol index note for navigation.\n\n### Phase 7: Documents\n\nProduce long-form documentation summarizing the codebase.\n\n### Phase 7B: Architecture\n\nCreate an architecture reference note linking all prior phases.\n\nSee [references\u002Fphases.md](references\u002Fphases.md) for full phase details.\n\n## Execution Order\n\n```text\n0 -> 1 -> 1B -> 2 -> 2B -> 3 -> 4 -> 5 -> 6 -> 6B -> 7 -> 7B\n```\n\n**Guidelines**:\n\n- Execute phases in order\n- Use Serena's `find_symbol` and `find_referencing_symbols`\n- Deduplicate notes before creating\n- Link notes via relations bidirectionally\n- Create summary notes for large documents\n\n## Memory Targets\n\n| Profile | Total Notes | Documents | Entities |\n|---------|-------------|-----------|----------|\n| Small Simple | 17-31 | 2 | 3-5 |\n| Small Complex | 28-46 | 2 | 5-10 |\n| Medium | 38-66 | 2-3 | 10-20 |\n| Large | 66-112 | 3-6 | 20-40 |\n\n## Quality Principles\n\n| Principle | Description |\n|-----------|-------------|\n| Symbol-accurate | Use LSP data, not guesses |\n| Atomic | One concept per note |\n| Size | 200-400 words ideal |\n| Linking | Connect related notes via relations |\n\n## Validation\n\nAfter encoding, verify all outputs meet quality standards:\n\n- [ ] Test search: \"How do I add a new API endpoint?\"\n- [ ] Test dependency query: \"What dependencies does this project use?\"\n- [ ] List notes by folder\n- [ ] Verify note relations\n- [ ] Check Symbol Index note exists\n- [ ] Check Architecture Reference note exists\n- [ ] All target components have Brain memory notes\n- [ ] Notes linked via relations\n- [ ] No duplicate notes in knowledge graph\n\nSee [references\u002Fvalidation.md](references\u002Fvalidation.md) for test commands.\n\n## Anti-Patterns\n\n| Avoid | Why | Instead |\n|-------|-----|---------|\n| Skipping Phase 0 discovery | Wastes effort on wrong project scope | Always assess project size and complexity first |\n| Creating non-atomic notes | Pollutes search results, hard to maintain | One concept per note, 200-400 words |\n| Duplicate notes | Bloats knowledge graph, inconsistent links | Deduplicate notes before creating |\n| Skipping validation | No confidence in encoding quality | Run validation checklist after completion |\n\n## References\n\n| Document | Content |\n|----------|---------|\n| [phases.md](references\u002Fphases.md) | Detailed phase workflows |\n| [templates.md](references\u002Ftemplates.md) | Note templates |\n| [validation.md](references\u002Fvalidation.md) | Validation test commands |\n\n## Related Skills\n\n- `\u002Fcode-symbols` - Serena symbol analysis\n- `\u002Fcode-architecture` - Architectural analysis with Brain memory\n",{"name":5,"model":31,"agents":32,"license":15,"metadata":34,"description":7},"claude-sonnet-4-5",[33,23],"analyst",{"version":35,"argument-hint":36},"1.1.0","Project path or name to encode (default: current directory)","main","2bd10cb7ca989f88dbf338b57957763718eda59b","templates\u002Fskills\u002Frepo-encoder","https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain","https:\u002F\u002Fgithub.com\u002Floriensleafs","2026-03-11 23:51:59",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add loriensleafs\u002Fbrain --skill repo-encoder",{"tool":49,"command":50},"bunx","bunx skills add loriensleafs\u002Fbrain --skill repo-encoder",{"tool":52,"command":53},"pnpm","pnpm dlx skills add loriensleafs\u002Fbrain --skill repo-encoder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Frepo-encoder\u002FSKILL.md",true,[57,63,67],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fphases.md","REFERENCE","参考文档",11801,"https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Frepo-encoder\u002Freferences\u002Fphases.md",{"path":64,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Ftemplates.md",3904,"https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Frepo-encoder\u002Freferences\u002Ftemplates.md",{"path":68,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fvalidation.md",1126,"https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Frepo-encoder\u002Freferences\u002Fvalidation.md",[72,88,104,126,147,170],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":26},"01M6CD3KHDHPR633RVP95G4XWN","validation-authority","Treat upstream validators as authoritative. Align local config to them. Use when validation fails unexpectedly, before modifying validator behavior, or when tempted to change upstream tool code.","https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fvalidation-authority\u002FSKILL.md",[],[79,80,81,82,83,84,85,23,86,87],"validation authority","validation","config","use","implementer","behavior","tool","code","change",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":26},"01M6CD3H29Q8FWN9YETT8YVQTS","using-brain-memory","Guidance for using Brain semantic memory effectively. Applies Zettelkasten atomic note principles with observations and relations. Use when deciding whether to query or create notes, structuring note content, or understanding the semantic knowledge graph.","https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fusing-forgetful-memory\u002FSKILL.md",[],[95,96,97,98,99,100,101,82,102,24,103],"using brain memory","memory","content","create","notes","graph","guidance","context","knowledge graph",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":26},"01M6CD3E2KTTMNSWXRJAAZA7D1","threat-modeling","Structured security analysis using OWASP Four-Question Framework and STRIDE methodology. Generates threat matrices with risk ratings, mitigations, and prioritization. Use for attack surface analysis, security architecture review, or when asking what can go wrong.","https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fthreat-modeling\u002FSKILL.md",[],[111,112,113,82,114,23,115,116,22,117,118,119,120,121,122,123,124,125],"threat","threat modeling","prioritization","question","architecture review","stride","risk","owasp","methodology","framework","security analysis","architecture","security","go","review",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":137,"publishedAt":26},"01M6CD3BC6G0Q2MDNW6X51XHBQ","taste-lints","Custom lints with agent-readable remediation instructions. Enforces taste invariants (file size, naming conventions, structured logging, complexity) and surfaces errors that agents can act on directly. Use when writing or reviewing code to catch style violations early.","https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Ftaste-lints\u002FSKILL.md",[132],{"categoryNo":133,"categoryName":134,"taxonomyType":135,"taxonomyTypeDesc":136},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[138,83,139,140,82,141,142,143,144,145,86,146],"taste lints","surfaces","complexity","instructions","remediation","file","logging","qa","writing",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":26},"01M6CD37Z7VD22BH42TG0GM66V","style-enforcement","Validate code against style rules from .editorconfig, StyleCop.json, and Directory.Build.props. Detects line ending violations, naming convention issues, indentation problems, and charset mismatches across C#, Python, TypeScript, and JavaScript. Produces JSON reports for pre-commit hooks and CI pipelines.","https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fstyle-enforcement\u002FSKILL.md",[],[154,155,156,157,21,158,83,159,160,161,162,163,145,164,86,165,166,167,168,169],"style enforcement","enforcement","ci","pipelines","hooks","Rules","json","pre-commit","editorconfig","reports","issues","validate","commit","javascript","python","typescript",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":176,"publishedAt":26},"01M6CD35JW73TPMCZBF9DTDEE8","steering-matcher","Match file paths against steering file glob patterns to determine applicable steering guidance. Use when orchestrator needs to inject context-aware guidance based on files being modified.","https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fsteering-matcher\u002FSKILL.md",[],[177,82,178,179,102,180,101,143],"steering matcher","files","haiku","orchestrator"]