[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DF02P8ZJPMDX0TARZ43BJR":3,"skill-same:01M6DF02P8ZJPMDX0TARZ43BJR":61},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":13,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":46,"install":47,"resources":60},"01M6DF02P8ZJPMDX0TARZ43BJR","gitnexus-impact-analysis",null,"Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: \"Is it safe to change X?\", \"What depends on this?\", \"What will break?\"","buihongduc132\u002Fopen-agent-sessions","buihongduc132","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5408008?v=4","01M6DEZ4EEM22HRP20MTWZWN21","01M6DEZ4NGS4CFW9ZDTCM2010S",0,"MIT","https:\u002F\u002Fgithub.com\u002Fbuihongduc132\u002Fopen-agent-sessions\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgitnexus\u002Fgitnexus-impact-analysis\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"analysis","impact analysis","gitnexus impact analysis","impact","gitnexus","safe","change","code","examples","Safety","editing","user","use","it","break","when","2026-11-10 10:12:30",false,"---\nname: \"cto-review\"\ndescription: \"\u002Fcs:cto-review \u003Cplan> — Architecture and scaling interrogation. Tech debt, scaling cliffs, team scaling, build-vs-buy. Use when committing to an architecture, planning for 10x load, or weighing a rebuild against a vendor.\"\n---\n\n# \u002Fcs:cto-review — CTO Forcing Questions\n\n**Command:** `\u002Fcs:cto-review \u003Cplan>`\n\nPressure-tests architecture and engineering scaling decisions. Six questions to surface the next scaling cliff before you hit it.\n\n## When to Run\n\n- Before approving a major architecture change\n- Before doubling the engineering team\n- Before a build-vs-buy decision > $100K\u002Fyear\n- When a system is showing reliability stress (SLOs missed)\n- Before committing to a new platform \u002F language \u002F DB\n\n## The Six CTO Questions\n\n### 1. Scaling Cliff\n**Where does the current architecture break, in terms of users \u002F requests \u002F data volume?**\n- Be specific. \"It breaks at 10× current load because the primary DB writes saturate.\"\n- If you don't know, run a load test before deciding.\n\n### 2. Tech Debt Inventory\n**What's the top tech debt item, what's it costing per week, and when does it become blocking?**\n```bash\npython ..\u002F..\u002F..\u002Fc-level-advisor\u002Fskills\u002Fcto-advisor\u002Fscripts\u002Ftech_debt_analyzer.py\n```\n\n### 3. Team Scaling\n**For each open req, what's the ramp time and contribution model?**\n```bash\npython ..\u002F..\u002F..\u002Fc-level-advisor\u002Fskills\u002Fcto-advisor\u002Fscripts\u002Fteam_scaling_calculator.py\n```\n\n### 4. Build vs Buy\n**Why are we building this instead of buying it — and what's the 3-year TCO of each?**\n- If \"we want control\" or \"it's not that hard\" — push back.\n- If the answer is \"this is our core moat,\" build.\n\n### 5. SLO \u002F Reliability\n**What are the SLOs for this system and what's the current error budget burn?**\n- Without an SLO, you can't reason about reliability tradeoffs.\n- See `engineering\u002Fslo-architect` for SLO design.\n\n### 6. Security & Compliance Surface\n**What does this expose, and has cs-ciso-advisor signed off?**\n- Architecture decisions are compliance decisions.\n- Loop in cs-ciso-advisor before commit.\n\n## Workflow\n\n1. Run the tech debt analyzer + team scaling calculator\n2. Define the scaling-cliff hypothesis explicitly\n3. Cross-check with cs-ciso-advisor for security implications\n4. Apply the verdict\n\n## Output Format\n\n```markdown\n# CTO Review: \u003Cplan>\n**Date:** YYYY-MM-DD\n\n## Scaling Cliff\n- Current capacity: \u003Cmetric>\n- Break point: \u003Cmetric>\n- Headroom: X months at current growth\n\n## Tech Debt\n- Top item: \u003Cdescription>\n- Cost per week: $X or N eng-hours\n- Blocking date estimate: \u003Cdate>\n\n## Team\n- Open reqs: N\n- Median ramp: X months\n- Contribution model: \u003Cpairing \u002F squad \u002F area>\n\n## Build vs Buy\n- 3-year build TCO: $X\n- 3-year buy TCO: $X\n- Strategic fit: \u003Ccore \u002F context>\n- Decision: BUILD | BUY\n\n## Reliability\n- SLO defined: yes \u002F no\n- Error budget burn: X% (target \u003C Y%)\n\n## Security\n- cs-ciso sign-off: ✅ \u002F ❌\n\n## Verdict\n? SHIP | ? SHARPEN | ? BLOCK\n\n## Next Steps\n[3 concrete actions]\n```\n\n## Routing\n\n- `\u002Fcs:ciso-review` — mandatory if data surface changes\n- `\u002Fcs:cfo-review` — for build-vs-buy > $100K\n- `\u002Fcs:execute` — quarterly plan\n- `\u002Fcs:boardroom` — for architecture pivots\n\n## Related\n\n- Agent: [`cs-cto-advisor`](..\u002F..\u002F..\u002Fagents\u002Fc-level\u002Fcs-cto-advisor.md)\n- Skill: [`cto-advisor`](..\u002F..\u002F..\u002Fc-level-advisor\u002Fskills\u002Fcto-advisor\u002FSKILL.md)\n- SLO: `..\u002F..\u002F..\u002Fengineering\u002Fslo-architect\u002F`\n\n---\n\n**Version:** 1.0.0\n","# \u002Fcs:cto-review — CTO Forcing Questions\n\n**Command:** `\u002Fcs:cto-review \u003Cplan>`\n\nPressure-tests architecture and engineering scaling decisions. Six questions to surface the next scaling cliff before you hit it.\n\n## When to Run\n\n- Before approving a major architecture change\n- Before doubling the engineering team\n- Before a build-vs-buy decision > $100K\u002Fyear\n- When a system is showing reliability stress (SLOs missed)\n- Before committing to a new platform \u002F language \u002F DB\n\n## The Six CTO Questions\n\n### 1. Scaling Cliff\n**Where does the current architecture break, in terms of users \u002F requests \u002F data volume?**\n- Be specific. \"It breaks at 10× current load because the primary DB writes saturate.\"\n- If you don't know, run a load test before deciding.\n\n### 2. Tech Debt Inventory\n**What's the top tech debt item, what's it costing per week, and when does it become blocking?**\n```bash\npython ..\u002F..\u002F..\u002Fc-level-advisor\u002Fskills\u002Fcto-advisor\u002Fscripts\u002Ftech_debt_analyzer.py\n```\n\n### 3. Team Scaling\n**For each open req, what's the ramp time and contribution model?**\n```bash\npython ..\u002F..\u002F..\u002Fc-level-advisor\u002Fskills\u002Fcto-advisor\u002Fscripts\u002Fteam_scaling_calculator.py\n```\n\n### 4. Build vs Buy\n**Why are we building this instead of buying it — and what's the 3-year TCO of each?**\n- If \"we want control\" or \"it's not that hard\" — push back.\n- If the answer is \"this is our core moat,\" build.\n\n### 5. SLO \u002F Reliability\n**What are the SLOs for this system and what's the current error budget burn?**\n- Without an SLO, you can't reason about reliability tradeoffs.\n- See `engineering\u002Fslo-architect` for SLO design.\n\n### 6. Security & Compliance Surface\n**What does this expose, and has cs-ciso-advisor signed off?**\n- Architecture decisions are compliance decisions.\n- Loop in cs-ciso-advisor before commit.\n\n## Workflow\n\n1. Run the tech debt analyzer + team scaling calculator\n2. Define the scaling-cliff hypothesis explicitly\n3. Cross-check with cs-ciso-advisor for security implications\n4. Apply the verdict\n\n## Output Format\n\n```markdown\n# CTO Review: \u003Cplan>\n**Date:** YYYY-MM-DD\n\n## Scaling Cliff\n- Current capacity: \u003Cmetric>\n- Break point: \u003Cmetric>\n- Headroom: X months at current growth\n\n## Tech Debt\n- Top item: \u003Cdescription>\n- Cost per week: $X or N eng-hours\n- Blocking date estimate: \u003Cdate>\n\n## Team\n- Open reqs: N\n- Median ramp: X months\n- Contribution model: \u003Cpairing \u002F squad \u002F area>\n\n## Build vs Buy\n- 3-year build TCO: $X\n- 3-year buy TCO: $X\n- Strategic fit: \u003Ccore \u002F context>\n- Decision: BUILD | BUY\n\n## Reliability\n- SLO defined: yes \u002F no\n- Error budget burn: X% (target \u003C Y%)\n\n## Security\n- cs-ciso sign-off: ✅ \u002F ❌\n\n## Verdict\n? SHIP | ? SHARPEN | ? BLOCK\n\n## Next Steps\n[3 concrete actions]\n```\n\n## Routing\n\n- `\u002Fcs:ciso-review` — mandatory if data surface changes\n- `\u002Fcs:cfo-review` — for build-vs-buy > $100K\n- `\u002Fcs:execute` — quarterly plan\n- `\u002Fcs:boardroom` — for architecture pivots\n\n## Related\n\n- Agent: [`cs-cto-advisor`](..\u002F..\u002F..\u002Fagents\u002Fc-level\u002Fcs-cto-advisor.md)\n- Skill: [`cto-advisor`](..\u002F..\u002F..\u002Fc-level-advisor\u002Fskills\u002Fcto-advisor\u002FSKILL.md)\n- SLO: `..\u002F..\u002F..\u002Fengineering\u002Fslo-architect\u002F`\n\n---\n\n**Version:** 1.0.0\n",{"name":39,"description":40},"cto-review","\u002Fcs:cto-review \u003Cplan> — Architecture and scaling interrogation. Tech debt, scaling cliffs, team scaling, build-vs-buy. Use when committing to an architecture, planning for 10x load, or weighing a rebuild against a vendor.","main","510dd2917e051cc953dc55f56fd6ef442aa01b38",".claude\u002Fskills\u002Fgitnexus\u002Fgitnexus-impact-analysis","https:\u002F\u002Fgithub.com\u002Fbuihongduc132\u002Fopen-agent-sessions","https:\u002F\u002Fgithub.com\u002Fbuihongduc132","2026-11-09 01:23:42",{"source":8,"skillName":39,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add buihongduc132\u002Fopen-agent-sessions --skill cto-review",{"tool":53,"command":54},"bunx","bunx skills add buihongduc132\u002Fopen-agent-sessions --skill cto-review",{"tool":56,"command":57},"pnpm","pnpm dlx skills add buihongduc132\u002Fopen-agent-sessions --skill cto-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbuihongduc132\u002Fopen-agent-sessions\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgitnexus\u002Fgitnexus-impact-analysis\u002FSKILL.md",true,[],[62,81,93,103,119,148],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":34},"01M6DF0MYWK0G3HD2XTNC6CFX7","worktree-lifecycle","Manage git worktrees for parallel development","https:\u002F\u002Fgithub.com\u002Fbuihongduc132\u002Fopen-agent-sessions\u002Fblob\u002Fmain\u002Ftest\u002Fskill-usage\u002Ffixtures\u002Fskill-inventory\u002Fworktree-lifecycle\u002FSKILL.md",[],[69,70,71,72,73,74,75,76,77,78,79,80],"worktree","lifecycle","worktree lifecycle","development","for","pi-agent","manage","worktrees","pi","git worktrees","parallel","git",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":34},"01M6DF0HZA6756KWDA7CN1GSEG","verifier-loop","Run verifier loop until all checks pass","https:\u002F\u002Fgithub.com\u002Fbuihongduc132\u002Fopen-agent-sessions\u002Fblob\u002Fmain\u002Ftest\u002Fskill-usage\u002Ffixtures\u002Fskill-inventory\u002Fverifier-loop\u002FSKILL.md",[],[88,89,90,74,77,91,92],"loop","verifier","verifier loop","verify","run",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":34},"01M6DF0F6KQFTND4SE7EW2HZ52","caveman","Terse communication style","https:\u002F\u002Fgithub.com\u002Fbuihongduc132\u002Fopen-agent-sessions\u002Fblob\u002Fmain\u002Ftest\u002Fskill-usage\u002Ffixtures\u002Fskill-inventory\u002Fcaveman\u002FSKILL.md",[],[95,100,101,74,102,77],"terse","communication","style",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":34},"01M6DF09EEJZ998F5E523E7TX6","gitnexus-refactoring","Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: \"Rename this function\", \"Extract this into a module\", \"Refactor this class\", \"Move this to a separate file\"","https:\u002F\u002Fgithub.com\u002Fbuihongduc132\u002Fopen-agent-sessions\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgitnexus\u002Fgitnexus-refactoring\u002FSKILL.md",[],[110,111,22,112,113,114,115,33,30,116,29,117,26,118,25],"gitnexus refactoring","refactoring","rename","move","split","module","extract","refactor","file",{"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":130,"publishedAt":34},"01M6DEZX88F69566J7HC637DB6","gitnexus-guide","Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: \"What GitNexus tools are available?\", \"How do I use GitNexus?\"","https:\u002F\u002Fgithub.com\u002Fbuihongduc132\u002Fopen-agent-sessions\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgitnexus\u002Fgitnexus-guide\u002FSKILL.md",[125],{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[131,132,22,133,30,33,134,135,136,137,138,139,140,29,141,142,143,26,144,145,146,147],"guide","gitnexus guide","graph schema","about","resources","how to","query","do","reference","schema","knowledge","how","Tools","knowledge graph","graph","workflow","MCP",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":34},"01M6DEZN5VZKWS8ARXD78X2K02","gitnexus-exploring","Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: \"How does X work?\", \"What calls this function?\", \"Show me the auth flow\"","https:\u002F\u002Fgithub.com\u002Fbuihongduc132\u002Fopen-agent-sessions\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgitnexus\u002Fgitnexus-exploring\u002FSKILL.md",[],[22,155,156,157,158,159,160,161,162,163,30,29,33,164,165,142,166,167,168,26,25,169,170],"gitnexus exploring","work","auth flow","what calls","trace execution","calls","flows","me","show","trace","explore","show me","execution","flow","architecture","auth"]