[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6RVH1BEW1YBBPE34NGTYTFB":3,"skill-same:01M6RVH1BEW1YBBPE34NGTYTFB":57},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":13,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":42,"install":43,"resources":56},"01M6RVH1BEW1YBBPE34NGTYTFB","kotlin-patterns",null,"Idiomatic Kotlin patterns, best practices, and conventions for building robust, efficient, and maintainable Kotlin applications with coroutines, null safety, and DSL builders.","sakamoto-family-smile\u002Fagent_monorepo","sakamoto-family-smile","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F132812403?v=4","01M6RTAT3H8PMWX5SJ65KP3VYF","01M6RTAV321WB5RAHCWTZMX5CV",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fkotlin-patterns\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29],"kotlin patterns","kotlin","patterns","best practices","Safety","applications","coroutines","conventions","with","for","idiomatic","dsl","2026-11-10 10:12:30",false,"---\nname: swe-orchestrator\ndescription: \"Orchestrates complete SDLC: Architect → Planner → Implementer (per-subtask) → Reviewer (per-subtask). Single entry point for complete feature development.\"\n---\n\n# ? SWE Orchestrator\n\n**Called By:** Issue author or team lead  \n**Input:** GitHub issue with requirements  \n**Output:** Merged feature branch, closed issue  \n**Duration:** Full feature lifecycle (hours to days)\n\n---\n\n## Quick Start\n\n**This skill orchestrates a COMPLETE feature end-to-end using 4 phases:**\n\n```\nPhase 1: swe-architect    → Analyze + diagram architecture\nPhase 2: swe-planner      → Break into subtasks + create .plan\u002F file\nPhase 3: swe-implementer  → Loop: implement each subtask (separate branch)\nPhase 4: swe-reviewer     → Loop: review each subtask + create MR\nPhase 5: Merge & Close    → Merge all MRs + close issue\n```\n\n**Source of Truth:** GitHub issue (requirements + approvals) + `.plan\u002F` file in repo (persistent state)\n\n---\n\n## Full Flow\n\n### Phase 1: Architecture Analysis\n1. Read issue requirements\n2. Call [swe-architect](..\u002Fswe-architect\u002FSKILL.md) → creates technical analysis + Mermaid diagram\n3. **MITM**: Present to USER → Get approval\n4. Post approved analysis to issue comment\n\n### Phase 2: Planning & Breakdown\n1. Call [swe-planner](..\u002Fswe-planner\u002FSKILL.md) with approved architecture\n2. Planner breaks into 3-8 subtasks and creates `.plan\u002F[issue]-[name].md`\n3. **MITM**: Present plan to USER → Get approval  \n4. Post approved plan to issue\n\n### Phase 3-4: Per-Subtask Loop (Repeat for each subtask)\n1. **Implement**: Call [swe-implementer](..\u002Fswe-implementer\u002FSKILL.md)\n   - Creates feature branch: `feature\u002F[issue]-[subtask-name]`\n   - Implements subtask locally\n   - Commits with message: `feat([scope]): [description]`\n2. **Review**: Call [swe-reviewer](..\u002Fswe-reviewer\u002FSKILL.md)\n   - Reviews quality gates (tests, code, coverage)\n   - Creates per-subtask MR\n   - Updates `.plan\u002F` with MR link\n3. **MITM**: Present to USER → \"MR #[N] ready for review?\"\n4. Update `.plan\u002F` with completion status and MR link\n5. Post subtask progress comment to issue\n\n### Phase 5: Merge & Completion\n1. Human reviewers approve and merge MRs\n2. Detect all MRs merged in `.plan\u002F` file\n3. Post final completion comment to issue\n4. Close issue (status: ? Complete)\n\n---\n\n## Master Progress Checklist\n\n```markdown\n- [ ] Phase 1: Architecture finalized\n- [ ] Phase 2: Plan + .plan\u002F file created  \n- [ ] Phase 3-4: All X subtasks done (Subtask 1, 2, 3...)\n- [ ] Phase 5: All MRs merged, issue closed\n```\n\n---\n\n## Critical Rules\n\n✅ **Issue = Single Source of Truth** - All approvals, decisions, blocker alerts post to issue\n\n✅ **`.plan\u002F` file tracks state** - Persistent progress file updated after each phase\n\n✅ **.plan\u002F file location** - `.plan\u002F[issue-number]-[feature-name].md`\n\n✅ **One subtask = One branch = One MR** - No bundling\n\n✅ **Architecture first** - No implementation starts without architect approval\n\n✅ **Quality gates mandatory** - swe-reviewer MUST verify all checks pass before MR\n\n✅ **context7 mandatory** - swe-implementer queries context7 before coding\n\n✅ **MITM at phase gates** - Present to USER before proceeding to next phase\n\n✅ **Conventional commits** - All commits follow `type(scope): message` format\n\n---\n\n## Exception Handling\n\n**IF blocked:** \n- Update `.plan\u002F` with status = ? BLOCKED\n- Post blocker report to issue\n- Alert USER\n\n**IF merge conflict:**\n- Re-run swe-implementer to rebase\n- Re-run swe-reviewer to validate\n- Post resolution to issue\n\n**IF scope changes mid-project:**\n- Return to Phase 1 (re-architect)\n- Update Phase 2 plan\n- Continue with Phase 3-4 as needed\n- Post scope change to issue\n\n**IF quality gate fails:**\n- swe-reviewer documents issue\n- swe-implementer addresses\n- swe-reviewer re-reviews\n- Loop until all checks pass\n\n---\n\n## Specialized Skills Orchestrated\n\n**Core 4-phase skills:**\n- [**swe-architect**](..\u002Fswe-architect\u002FSKILL.md) - Phase 1: Architecture analysis\n- [**swe-planner**](..\u002Fswe-planner\u002FSKILL.md) - Phase 2: Decompose into subtasks\n- [**swe-implementer**](..\u002Fswe-implementer\u002FSKILL.md) - Phase 3: Implement per-subtask\n- [**swe-reviewer**](..\u002Fswe-reviewer\u002FSKILL.md) - Phase 4: Review + create MR\n\n**Supporting skills:**\n- [**vcs-issue-management**](..\u002Fvcs-issue-management\u002FSKILL.md) - Issue comments + templates\n- [**vcs-branch**](..\u002Fvcs-branch\u002FSKILL.md) - Branch creation + sync\n- [**vcs-commit**](..\u002Fvcs-commit\u002FSKILL.md) - Conventional commits\n- [**vcs-change-request**](..\u002Fvcs-change-request\u002FSKILL.md) - MR\u002FPR creation\n- **context7 MCP** - Query for documentation + context\n- [**mermaid-diagrams**](..\u002Fmermaid-diagrams\u002FSKILL.md) - Architecture diagrams\n- [**backend-coder**](..\u002Fbackend-coder\u002FSKILL.md) - Code quality standards\n\n---\n\n## When to Use This Skill\n\n**Use orchestrator when:**\n- Starting a new GitHub issue that requires implementation\n- Issue is ready with clear requirements\n- Need full end-to-end feature delivery (architecture → code → review → merge)\n- Team wants coordinated, auditable workflow\n\n**DO NOT use orchestrator when:**\n- Just reviewing an existing MR (use swe-pr-reviewer instead)\n- Quick bug fix requiring no planning (use swe-implementer + swe-reviewer directly)\n- Only architectural analysis needed (use swe-architect alone)\n","# ? SWE Orchestrator\n\n**Called By:** Issue author or team lead  \n**Input:** GitHub issue with requirements  \n**Output:** Merged feature branch, closed issue  \n**Duration:** Full feature lifecycle (hours to days)\n\n---\n\n## Quick Start\n\n**This skill orchestrates a COMPLETE feature end-to-end using 4 phases:**\n\n```\nPhase 1: swe-architect    → Analyze + diagram architecture\nPhase 2: swe-planner      → Break into subtasks + create .plan\u002F file\nPhase 3: swe-implementer  → Loop: implement each subtask (separate branch)\nPhase 4: swe-reviewer     → Loop: review each subtask + create MR\nPhase 5: Merge & Close    → Merge all MRs + close issue\n```\n\n**Source of Truth:** GitHub issue (requirements + approvals) + `.plan\u002F` file in repo (persistent state)\n\n---\n\n## Full Flow\n\n### Phase 1: Architecture Analysis\n1. Read issue requirements\n2. Call [swe-architect](..\u002Fswe-architect\u002FSKILL.md) → creates technical analysis + Mermaid diagram\n3. **MITM**: Present to USER → Get approval\n4. Post approved analysis to issue comment\n\n### Phase 2: Planning & Breakdown\n1. Call [swe-planner](..\u002Fswe-planner\u002FSKILL.md) with approved architecture\n2. Planner breaks into 3-8 subtasks and creates `.plan\u002F[issue]-[name].md`\n3. **MITM**: Present plan to USER → Get approval  \n4. Post approved plan to issue\n\n### Phase 3-4: Per-Subtask Loop (Repeat for each subtask)\n1. **Implement**: Call [swe-implementer](..\u002Fswe-implementer\u002FSKILL.md)\n   - Creates feature branch: `feature\u002F[issue]-[subtask-name]`\n   - Implements subtask locally\n   - Commits with message: `feat([scope]): [description]`\n2. **Review**: Call [swe-reviewer](..\u002Fswe-reviewer\u002FSKILL.md)\n   - Reviews quality gates (tests, code, coverage)\n   - Creates per-subtask MR\n   - Updates `.plan\u002F` with MR link\n3. **MITM**: Present to USER → \"MR #[N] ready for review?\"\n4. Update `.plan\u002F` with completion status and MR link\n5. Post subtask progress comment to issue\n\n### Phase 5: Merge & Completion\n1. Human reviewers approve and merge MRs\n2. Detect all MRs merged in `.plan\u002F` file\n3. Post final completion comment to issue\n4. Close issue (status: ? Complete)\n\n---\n\n## Master Progress Checklist\n\n```markdown\n- [ ] Phase 1: Architecture finalized\n- [ ] Phase 2: Plan + .plan\u002F file created  \n- [ ] Phase 3-4: All X subtasks done (Subtask 1, 2, 3...)\n- [ ] Phase 5: All MRs merged, issue closed\n```\n\n---\n\n## Critical Rules\n\n✅ **Issue = Single Source of Truth** - All approvals, decisions, blocker alerts post to issue\n\n✅ **`.plan\u002F` file tracks state** - Persistent progress file updated after each phase\n\n✅ **.plan\u002F file location** - `.plan\u002F[issue-number]-[feature-name].md`\n\n✅ **One subtask = One branch = One MR** - No bundling\n\n✅ **Architecture first** - No implementation starts without architect approval\n\n✅ **Quality gates mandatory** - swe-reviewer MUST verify all checks pass before MR\n\n✅ **context7 mandatory** - swe-implementer queries context7 before coding\n\n✅ **MITM at phase gates** - Present to USER before proceeding to next phase\n\n✅ **Conventional commits** - All commits follow `type(scope): message` format\n\n---\n\n## Exception Handling\n\n**IF blocked:** \n- Update `.plan\u002F` with status = ? BLOCKED\n- Post blocker report to issue\n- Alert USER\n\n**IF merge conflict:**\n- Re-run swe-implementer to rebase\n- Re-run swe-reviewer to validate\n- Post resolution to issue\n\n**IF scope changes mid-project:**\n- Return to Phase 1 (re-architect)\n- Update Phase 2 plan\n- Continue with Phase 3-4 as needed\n- Post scope change to issue\n\n**IF quality gate fails:**\n- swe-reviewer documents issue\n- swe-implementer addresses\n- swe-reviewer re-reviews\n- Loop until all checks pass\n\n---\n\n## Specialized Skills Orchestrated\n\n**Core 4-phase skills:**\n- [**swe-architect**](..\u002Fswe-architect\u002FSKILL.md) - Phase 1: Architecture analysis\n- [**swe-planner**](..\u002Fswe-planner\u002FSKILL.md) - Phase 2: Decompose into subtasks\n- [**swe-implementer**](..\u002Fswe-implementer\u002FSKILL.md) - Phase 3: Implement per-subtask\n- [**swe-reviewer**](..\u002Fswe-reviewer\u002FSKILL.md) - Phase 4: Review + create MR\n\n**Supporting skills:**\n- [**vcs-issue-management**](..\u002Fvcs-issue-management\u002FSKILL.md) - Issue comments + templates\n- [**vcs-branch**](..\u002Fvcs-branch\u002FSKILL.md) - Branch creation + sync\n- [**vcs-commit**](..\u002Fvcs-commit\u002FSKILL.md) - Conventional commits\n- [**vcs-change-request**](..\u002Fvcs-change-request\u002FSKILL.md) - MR\u002FPR creation\n- **context7 MCP** - Query for documentation + context\n- [**mermaid-diagrams**](..\u002Fmermaid-diagrams\u002FSKILL.md) - Architecture diagrams\n- [**backend-coder**](..\u002Fbackend-coder\u002FSKILL.md) - Code quality standards\n\n---\n\n## When to Use This Skill\n\n**Use orchestrator when:**\n- Starting a new GitHub issue that requires implementation\n- Issue is ready with clear requirements\n- Need full end-to-end feature delivery (architecture → code → review → merge)\n- Team wants coordinated, auditable workflow\n\n**DO NOT use orchestrator when:**\n- Just reviewing an existing MR (use swe-pr-reviewer instead)\n- Quick bug fix requiring no planning (use swe-implementer + swe-reviewer directly)\n- Only architectural analysis needed (use swe-architect alone)\n",{"name":35,"description":36},"swe-orchestrator","Orchestrates complete SDLC: Architect → Planner → Implementer (per-subtask) → Reviewer (per-subtask). Single entry point for complete feature development.","main","900221604dab32b1c1562a736204b21aae727b73",".claude\u002Fskills\u002Fecc\u002Fkotlin-patterns","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile","2026-11-08 20:29:14",{"source":8,"skillName":35,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add sakamoto-family-smile\u002Fagent_monorepo --skill swe-orchestrator",{"tool":49,"command":50},"bunx","bunx skills add sakamoto-family-smile\u002Fagent_monorepo --skill swe-orchestrator",{"tool":52,"command":53},"pnpm","pnpm dlx skills add sakamoto-family-smile\u002Fagent_monorepo --skill swe-orchestrator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fkotlin-patterns\u002FSKILL.md",true,[],[58,91,99,119,142,169],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":72,"publishedAt":30},"01M6RW50THEFSKK42YNR8XFZA1","remotion-video-creation","Best practices for Remotion - Video creation in React. 29 domain-specific rules covering 3D, animations, audio, captions, charts, transitions, and more.","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fremotion-video-creation\u002FSKILL.md",[64,69],{"categoryNo":65,"categoryName":66,"taxonomyType":67,"taxonomyTypeDesc":68},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":70,"categoryName":71,"taxonomyType":67,"taxonomyTypeDesc":68},"01JBSEEDCAT000000000000016","图像与多媒体",[73,74,75,76,77,78,79,80,81,82,83,21,84,85,86,87,88,89,90,27],"Video","remotion video","remotion video creation","creation","Remotion","Charts","Captions","Audio","3D","Composition","Animation","more","animations","domain-specific","domain","three","Rules","Lottie",{"skillNo":92,"name":93,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":30},"01M6VCJ23NPECPSZJKGY691F75","hotcook-recipes","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002Fhotcook-agent\u002Fdata\u002Fskills\u002Fhotcook-recipes\u002FSKILL.md",[],[97,98],"hotcook recipes","recipes",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":113,"publishedAt":30},"01M6VCHHE00X5XHSDRD1KH1BW2","code-helper","Code review and assistance skill","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002Fagent-system-2\u002Fskills\u002Fcode-helper\u002Fskill.md",[105,108],{"categoryNo":106,"categoryName":107,"taxonomyType":67,"taxonomyTypeDesc":68},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[114,115,116,117,118],"code helper","helper","code","code review","review",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":131,"publishedAt":30},"01M6VCH3Q31A20H6SQ1H0J7JB2","research-assistant","Web research assistant skill using Brave Search MCP","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002Fagent-system-1\u002Fskills\u002Fresearch-assistant\u002Fskill.md",[125,128],{"categoryNo":126,"categoryName":127,"taxonomyType":67,"taxonomyTypeDesc":68},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":129,"categoryName":130,"taxonomyType":67,"taxonomyTypeDesc":68},"01JBSEEDCAT000000000000023","Skill与智能体开发",[132,133,134,135,136,137,138,139,140,141],"research assistant","research","assistant","MCP","web","search","brave search","web research","brave","web research assistant",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":152,"publishedAt":30},"01M6VCGZZGPNVJSCZ1JTMNZAHY","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fx-api\u002FSKILL.md",[148,151],{"categoryNo":149,"categoryName":150,"taxonomyType":67,"taxonomyTypeDesc":68},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},[153,154,26,155,156,157,27,158,159,160,161,162,20,163,164,165,166,167,137,168],"x api","api","when","limits","rate","threads","reading","native","posting","platform","api integration","twitter","use","auth","analytics","OAuth",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":176,"publishedAt":30},"01M6VCGVX6DGB1FKTA53QBBCQB","workspace-surface-audit","Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fworkspace-surface-audit\u002FSKILL.md",[175],{"categoryNo":129,"categoryName":130,"taxonomyType":67,"taxonomyTypeDesc":68},[177,178,179,180,135,181,182,116,183,184,185,186,165,187,188,189,190,160,191,155],"workspace surface audit","workspace","audit","hooks","workflows","connectors","capabilities","harness","repo","environment","up","harness setup","active","env","value"]