[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NTEWY8CJJQSFBVSAFGP9PE":3,"skill-same:01M6NTEWY8CJJQSFBVSAFGP9PE":51},{"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":24,"linkOnly":25,"markdownContent":26,"markdownBody":27,"frontMatter":28,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M6NTEWY8CJJQSFBVSAFGP9PE","completion-check",null,"Completion Check: Verify Infrastructure Is Wired","rubicanjr\u002FFinCognis","rubicanjr","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F234912519?v=4","01M6NT156NND8J474G34SB3923","Rubi","01M6NT15B70RWXE1N3YV0BZY8A",0,"MIT","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fcompletion-check\u002FSKILL.md",[],[19,20,21,22,23],"check","completion check","infrastructure","verify","false","2026-11-10 10:12:30",false,"---\nname: completion-check\ndescription: \"Completion Check: Verify Infrastructure Is Wired\"\nuser-invocable: false\n---\n\n# Completion Check: Verify Infrastructure Is Wired\n\nWhen building infrastructure, verify it's actually connected to the system before marking as complete.\n\n## Pattern\n\nInfrastructure is not done when the code is written - it's done when it's wired into the system and actively used. Dead code (built but never called) is wasted effort.\n\n## DO\n\n1. **Trace the execution path** - Follow from user intent to actual code execution:\n   ```bash\n   # Example: Verify Task tool spawns correctly\n   grep -r \"claude -p\" src\u002F\n   grep -r \"Task(\" src\u002F\n   ```\n\n2. **Check hooks are registered**, not just implemented:\n   ```bash\n   # Hook exists?\n   ls -la .claude\u002Fhooks\u002Fmy-hook.sh\n\n   # Hook registered in settings?\n   grep \"my-hook\" .claude\u002Fsettings.json\n   ```\n\n3. **Verify database connections** - Ensure infrastructure uses the right backend:\n   ```bash\n   # Check connection strings\n   grep -r \"postgresql:\u002F\u002F\" src\u002F\n   grep -r \"sqlite:\" src\u002F  # Should NOT find if PostgreSQL expected\n   ```\n\n4. **Test end-to-end** - Run the feature and verify infrastructure is invoked:\n   ```bash\n   # Add debug logging\n   echo \"DEBUG: DAG spawn invoked\" >> \u002Ftmp\u002Fdebug.log\n\n   # Trigger feature\n   uv run python -m my_feature\n\n   # Verify infrastructure was called\n   cat \u002Ftmp\u002Fdebug.log\n   ```\n\n5. **Search for orphaned implementations**:\n   ```bash\n   # Find functions defined but never called\n   ast-grep --pattern 'async function $NAME() { $$$ }' | \\\n     xargs -I {} grep -r \"{}\" src\u002F\n   ```\n\n## DON'T\n\n- Mark infrastructure \"complete\" without testing execution path\n- Assume code is wired just because it exists\n- Build parallel systems (Task tool vs claude -p spawn)\n- Use wrong backends (SQLite when PostgreSQL is architected)\n- Skip end-to-end testing (\"it compiles\" ≠ \"it runs\")\n\n## Completion Checklist\n\nBefore declaring infrastructure complete:\n\n- [ ] Traced execution path from entry point to infrastructure\n- [ ] Verified hooks are registered in .claude\u002Fsettings.json\n- [ ] Confirmed correct database\u002Fbackend in use\n- [ ] Ran end-to-end test showing infrastructure invoked\n- [ ] Searched for dead code or parallel implementations\n- [ ] Checked configuration files match implementation\n\n## Example: DAG Task Graph\n\n**Wrong approach:**\n```\n✓ Built BeadsTaskGraph class\n✓ Implemented DAG dependencies\n✓ Added spawn logic\n✗ Never wired - Task tool still runs instead\n✗ Used SQLite instead of PostgreSQL\n```\n\n**Right approach:**\n```\n✓ Built BeadsTaskGraph class\n✓ Wired into Task tool execution path\n✓ Verified claude -p spawn is called\n✓ Confirmed PostgreSQL backend in use\n✓ Tested: user calls Task() → DAG spawns → beads execute\n✓ No parallel implementations found\n```\n\n## Source Sessions\n\n- This session: Architecture gap discovery - DAG built but not wired, Task tool runs instead of spawn, SQLite used instead of PostgreSQL\n","# Completion Check: Verify Infrastructure Is Wired\n\nWhen building infrastructure, verify it's actually connected to the system before marking as complete.\n\n## Pattern\n\nInfrastructure is not done when the code is written - it's done when it's wired into the system and actively used. Dead code (built but never called) is wasted effort.\n\n## DO\n\n1. **Trace the execution path** - Follow from user intent to actual code execution:\n   ```bash\n   # Example: Verify Task tool spawns correctly\n   grep -r \"claude -p\" src\u002F\n   grep -r \"Task(\" src\u002F\n   ```\n\n2. **Check hooks are registered**, not just implemented:\n   ```bash\n   # Hook exists?\n   ls -la .claude\u002Fhooks\u002Fmy-hook.sh\n\n   # Hook registered in settings?\n   grep \"my-hook\" .claude\u002Fsettings.json\n   ```\n\n3. **Verify database connections** - Ensure infrastructure uses the right backend:\n   ```bash\n   # Check connection strings\n   grep -r \"postgresql:\u002F\u002F\" src\u002F\n   grep -r \"sqlite:\" src\u002F  # Should NOT find if PostgreSQL expected\n   ```\n\n4. **Test end-to-end** - Run the feature and verify infrastructure is invoked:\n   ```bash\n   # Add debug logging\n   echo \"DEBUG: DAG spawn invoked\" >> \u002Ftmp\u002Fdebug.log\n\n   # Trigger feature\n   uv run python -m my_feature\n\n   # Verify infrastructure was called\n   cat \u002Ftmp\u002Fdebug.log\n   ```\n\n5. **Search for orphaned implementations**:\n   ```bash\n   # Find functions defined but never called\n   ast-grep --pattern 'async function $NAME() { $$$ }' | \\\n     xargs -I {} grep -r \"{}\" src\u002F\n   ```\n\n## DON'T\n\n- Mark infrastructure \"complete\" without testing execution path\n- Assume code is wired just because it exists\n- Build parallel systems (Task tool vs claude -p spawn)\n- Use wrong backends (SQLite when PostgreSQL is architected)\n- Skip end-to-end testing (\"it compiles\" ≠ \"it runs\")\n\n## Completion Checklist\n\nBefore declaring infrastructure complete:\n\n- [ ] Traced execution path from entry point to infrastructure\n- [ ] Verified hooks are registered in .claude\u002Fsettings.json\n- [ ] Confirmed correct database\u002Fbackend in use\n- [ ] Ran end-to-end test showing infrastructure invoked\n- [ ] Searched for dead code or parallel implementations\n- [ ] Checked configuration files match implementation\n\n## Example: DAG Task Graph\n\n**Wrong approach:**\n```\n✓ Built BeadsTaskGraph class\n✓ Implemented DAG dependencies\n✓ Added spawn logic\n✗ Never wired - Task tool still runs instead\n✗ Used SQLite instead of PostgreSQL\n```\n\n**Right approach:**\n```\n✓ Built BeadsTaskGraph class\n✓ Wired into Task tool execution path\n✓ Verified claude -p spawn is called\n✓ Confirmed PostgreSQL backend in use\n✓ Tested: user calls Task() → DAG spawns → beads execute\n✓ No parallel implementations found\n```\n\n## Source Sessions\n\n- This session: Architecture gap discovery - DAG built but not wired, Task tool runs instead of spawn, SQLite used instead of PostgreSQL\n",{"name":5,"description":7,"user-invocable":25},"main","70e1c350500ee750987420bbae48837afa906b7e","skills\u002Fcompletion-check","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis","https:\u002F\u002Fgithub.com\u002Frubicanjr","linktr.ee\u002Ffinanskodu","Industrial Engineer & CIO @FinansKodu. Architecting AI-driven financial agents and autonomous workflows. 🏗️ Building systems, not just prompts.","2026-06-09 13:50:15",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add rubicanjr\u002FFinCognis --skill completion-check",{"tool":43,"command":44},"bunx","bunx skills add rubicanjr\u002FFinCognis --skill completion-check",{"tool":46,"command":47},"pnpm","pnpm dlx skills add rubicanjr\u002FFinCognis --skill completion-check","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fcompletion-check\u002FSKILL.md",true,[],[52,73,81,101,131,150],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":63,"publishedAt":24},"01M6NWS9DAXJTADT4T5MB49X8W","workflow-router","Goal-based workflow orchestration - routes tasks to specialist agents based on user goals","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-router\u002FSKILL.md",[58],{"categoryNo":59,"categoryName":60,"taxonomyType":61,"taxonomyTypeDesc":62},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[64,65,66,67,68,69,70,71,72],"workflow router","workflow","router","orchestration","goals","goal","user","workflow orchestration","tasks",{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":24},"01M6NWS3RETSC0SHP16HP66E14","wiring","Wiring Verification","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fwiring\u002FSKILL.md",[],[75,80,23],"verification",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":90,"publishedAt":24},"01M6NWS0XW9CVQZBDA1EGW0TWC","websocket-patterns","Connection management, room patterns, reconnection strategies, message buffering, and binary protocol design.","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fwebsocket-patterns\u002Fskill.md",[87],{"categoryNo":88,"categoryName":89,"taxonomyType":61,"taxonomyTypeDesc":62},"01JBSEEDCAT000000000000015","视觉设计",[91,92,93,94,95,96,97,98,99,100],"websocket","patterns","websocket patterns","design","protocol","management","message","strategies","binary","connection",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":111,"publishedAt":24},"01M6NWRDQDX9ZNETAWRRMQWV52","visual-verdict","Screenshot comparison QA for frontend development. Takes a screenshot of the current implementation, scores it across multiple visual dimensions, and returns a structured PASS\u002FREVISE\u002FFAIL verdict with concrete fixes. Use when implementing UI from a design reference or verifying visual correctness.","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fvisual-verdict\u002FSKILL.md",[107,110],{"categoryNo":108,"categoryName":109,"taxonomyType":61,"taxonomyTypeDesc":62},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":59,"categoryName":60,"taxonomyType":61,"taxonomyTypeDesc":62},[112,113,114,115,116,117,118,119,120,121,122,123,124,94,125,126,127,128,129,130],"visual","verdict","visual verdict","ui","across","revise","comparison","correctness","implementing","for","fixes","dimensions","frontend","development","qa","screenshot","returns","use","frontend development",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":24},"01M6NWR8HSNRS7MNDK2J02QYMN","verification-loop","Comprehensive verification system covering build, types, lint, tests, security, and diff review before a PR.","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[138,139,80,140,141,142,143,144,145,146,147,148,149],"verification loop","loop","lint","review","security","pr","system","diff","build","tests","diff review","types",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":24},"01M6NWR4HHSFR0VR5EXFRWA747","vector-db-patterns","Embedding strategies, ANN algorithms, hybrid search, RAG chunking strategies, and reranking for semantic search and retrieval.","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fvector-db-patterns\u002Fskill.md",[],[157,158,159,160,92,161,162,163,164,98,165,166,167,168,169,121,170,171],"vector db patterns","vector db","db","vector","semantic search","search","embedding strategies","algorithms","chunking","semantic","retrieval","embedding","Hybrid Search","hybrid","rag"]