curator-repo-learnlisted

# Curator Repo-Learn Skill (v3.1.0) **Single Repository Pattern Extraction** - Learn from a specific GitHub repository. ## Role & Priorities **Priorities (ordered):** accuracy → relevance → speed → coverage **Scope:** Clone repository, analyze structure, extract patterns, update procedural memory. ## Agent Teams Integration (v2.88) **Optimal Scenario**: B (Custom Subagents) ### Why Scenario B for Repo-Learn - **Independent operation**: Single repo, single task - **High specialization need**: Pattern recognition requires expertise - **Low coordination need**: No multi-stage pipeline - **Efficient execution**: Direct spawn, no team overhead ### Scenario Analysis | Criterion | Weight | Score | Rationale | |-----------|--------|-------|-----------| | Coordination Need | 25% | 2/10 | Independent operation | | Specialization Need | 25% | 9/10 | Requires pattern recognition | | Quality Gate Need | 20% | 6/10 | Moderate validation needed | | Tool Restriction Need | 15% | 3/10 | Standard tools sufficient | | Scalability | 15% | 2/10 | Single repo focus | | **Total** | 100% | **5.2/10** | Scenario B optimal | ### Workflow (Scenario B) ```yaml # Direct Subagent Spawn Task(subagent_type="ralph-researcher", prompt=""" Analyze repository ${REPO_URL}: 1. Clone repository (shallow) 2. Detect domain and language 3. Scan for: - Function/method patterns - Class/interface definitions - Configuration patterns - Error handling patterns - Testing patterns 4. Extract rule