[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75WVGKHSMPQWQS3C96EA3ZP":3,"skill-same:01M75WVGKHSMPQWQS3C96EA3ZP":50},{"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":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M75WVGKHSMPQWQS3C96EA3ZP","caveman-review",null,"Compressed code review - one line per finding with location, problem and fix. Use for \u002Fcaveman-review, \"review this PR\", or \"review the diff\".","Wifabric\u002FAISC","Wifabric","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F330220688?v=4","01M75WHNJBRX6BCM6XZKHHFC16","01M75WHNJZSW18JZJBRAPZJ5RV",7,"MIT","https:\u002F\u002Fgithub.com\u002FWifabric\u002FAISC\u002Fblob\u002Fmain\u002Fcontainer\u002F_bundle\u002Fplugins\u002Fmarketplaces\u002Fcaveman\u002Fskills\u002Fcaveman-review\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: caveman-review\ndescription: >\n  Compressed code review - one line per finding with location, problem and fix.\n  Use for \u002Fcaveman-review, \"review this PR\", or \"review the diff\".\n---\n\nWrite code review comments terse and actionable. One line per finding. Location, problem, fix. No throat-clearing.\n\n## Rules\n\n**Format:** `L\u003Cline>: \u003Cproblem>. \u003Cfix>.` — or `\u003Cfile>:L\u003Cline>: ...` when reviewing multi-file diffs.\n\n**Severity prefix (optional, when mixed):**\n- `🔴 bug:` — broken behavior, will cause incident\n- `🟡 risk:` — works but fragile (race, missing null check, swallowed error)\n- `🔵 nit:` — style, naming, micro-optim. Author can ignore\n- `❓ q:` — genuine question, not a suggestion\n\n**Drop:**\n- \"I noticed that...\", \"It seems like...\", \"You might want to consider...\"\n- \"This is just a suggestion but...\" — use `nit:` instead\n- \"Great work!\", \"Looks good overall but...\" — say it once at the top, not per comment\n- Restating what the line does — the reviewer can read the diff\n- Hedging (\"perhaps\", \"maybe\", \"I think\") — if unsure use `q:`\n\n**Keep:**\n- Exact line numbers\n- Exact symbol\u002Ffunction\u002Fvariable names in backticks\n- Concrete fix, not \"consider refactoring this\"\n- The *why* if the fix isn't obvious from the problem statement\n\n## Examples\n\n❌ \"I noticed that on line 42 you're not checking if the user object is null before accessing the email property. This could potentially cause a crash if the user is not found in the database. You might want to add a null check here.\"\n\n✅ `L42: 🔴 bug: user can be null after .find(). Add guard before .email.`\n\n❌ \"It looks like this function is doing a lot of things and might benefit from being broken up into smaller functions for readability.\"\n\n✅ `L88-140: 🔵 nit: 50-line fn does 4 things. Extract validate\u002Fnormalize\u002Fpersist.`\n\n❌ \"Have you considered what happens if the API returns a 429? I think we should probably handle that case.\"\n\n✅ `L23: 🟡 risk: no retry on 429. Wrap in withBackoff(3).`\n\n## Auto-Clarity\n\nDrop terse mode for: security findings (CVE-class bugs need full explanation + reference), architectural disagreements (need rationale, not just a one-liner), and onboarding contexts where the author is new and needs the \"why\". In those cases write a normal paragraph, then resume terse for the rest.\n\n## Boundaries\n\nReviews only — does not write the code fix, does not approve\u002Frequest-changes, does not run linters. Output the comment(s) ready to paste into the PR. \"stop caveman-review\" or \"normal mode\": revert to verbose review style.","Write code review comments terse and actionable. One line per finding. Location, problem, fix. No throat-clearing.\n\n## Rules\n\n**Format:** `L\u003Cline>: \u003Cproblem>. \u003Cfix>.` — or `\u003Cfile>:L\u003Cline>: ...` when reviewing multi-file diffs.\n\n**Severity prefix (optional, when mixed):**\n- `🔴 bug:` — broken behavior, will cause incident\n- `🟡 risk:` — works but fragile (race, missing null check, swallowed error)\n- `🔵 nit:` — style, naming, micro-optim. Author can ignore\n- `❓ q:` — genuine question, not a suggestion\n\n**Drop:**\n- \"I noticed that...\", \"It seems like...\", \"You might want to consider...\"\n- \"This is just a suggestion but...\" — use `nit:` instead\n- \"Great work!\", \"Looks good overall but...\" — say it once at the top, not per comment\n- Restating what the line does — the reviewer can read the diff\n- Hedging (\"perhaps\", \"maybe\", \"I think\") — if unsure use `q:`\n\n**Keep:**\n- Exact line numbers\n- Exact symbol\u002Ffunction\u002Fvariable names in backticks\n- Concrete fix, not \"consider refactoring this\"\n- The *why* if the fix isn't obvious from the problem statement\n\n## Examples\n\n❌ \"I noticed that on line 42 you're not checking if the user object is null before accessing the email property. This could potentially cause a crash if the user is not found in the database. You might want to add a null check here.\"\n\n✅ `L42: 🔴 bug: user can be null after .find(). Add guard before .email.`\n\n❌ \"It looks like this function is doing a lot of things and might benefit from being broken up into smaller functions for readability.\"\n\n✅ `L88-140: 🔵 nit: 50-line fn does 4 things. Extract validate\u002Fnormalize\u002Fpersist.`\n\n❌ \"Have you considered what happens if the API returns a 429? I think we should probably handle that case.\"\n\n✅ `L23: 🟡 risk: no retry on 429. Wrap in withBackoff(3).`\n\n## Auto-Clarity\n\nDrop terse mode for: security findings (CVE-class bugs need full explanation + reference), architectural disagreements (need rationale, not just a one-liner), and onboarding contexts where the author is new and needs the \"why\". In those cases write a normal paragraph, then resume terse for the rest.\n\n## Boundaries\n\nReviews only — does not write the code fix, does not approve\u002Frequest-changes, does not run linters. Output the comment(s) ready to paste into the PR. \"stop caveman-review\" or \"normal mode\": revert to verbose review style.",{"name":5,"description":7},"main","1c39903dc146e00ac5b7d92c8bd48433a3d4a7f5","container\u002F_bundle\u002Fplugins\u002Fmarketplaces\u002Fcaveman\u002Fskills\u002Fcaveman-review",0,"https:\u002F\u002Fgithub.com\u002FWifabric\u002FAISC","https:\u002F\u002Fgithub.com\u002FWifabric","2026-11-09 21:53:05",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add Wifabric\u002FAISC --skill caveman-review",{"tool":36,"command":37},"bunx","bunx skills add Wifabric\u002FAISC --skill caveman-review",{"tool":39,"command":40},"pnpm","pnpm dlx skills add Wifabric\u002FAISC --skill caveman-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FWifabric\u002FAISC\u002Fblob\u002Fmain\u002Fcontainer\u002F_bundle\u002Fplugins\u002Fmarketplaces\u002Fcaveman\u002Fskills\u002Fcaveman-review\u002FSKILL.md",true,[44],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"README.md","REFERENCE","参考文档",1210,"https:\u002F\u002Fgithub.com\u002FWifabric\u002FAISC\u002Fblob\u002Fmain\u002Fcontainer\u002F_bundle\u002Fplugins\u002Fmarketplaces\u002Fcaveman\u002Fskills\u002Fcaveman-review\u002FREADME.md",[51,58,65,72,80,88],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M75WYM5HQ22465HVJ6FQW8ES","topic-workshop","围绕用户选定的主题，把资料、沟通、实践与反馈沉淀为可执行的主题手册，并记录迭代依据。用于建立或接续长期主题工作、从实践完善手册、分析流程改进；单次问答、纯文件摘要和普通代码修改不自动启动本流程。","https:\u002F\u002Fgithub.com\u002FWifabric\u002FAISC\u002Fblob\u002Fmain\u002Fsrc\u002Faisc\u002F_topic_skill\u002FSKILL.md",[],[],{"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":64,"publishedAt":18},"01M75WYJGGHSD17YXV881RZVE9","aisc-development","推进 AISC 已确认版本的功能开发、Issue 修复、贡献者 PR 集成与统一 Preview 交付。用于本仓库开发协作，不用于平台内安装扩展技能或替用户批准产品与正式发布。","https:\u002F\u002Fgithub.com\u002FWifabric\u002FAISC\u002Fblob\u002Fmain\u002Fskills\u002Faisc-development\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M75WYGD0HHMQYJTEV1KKV2FX","karpathy-guidelines","Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.","https:\u002F\u002Fgithub.com\u002FWifabric\u002FAISC\u002Fblob\u002Fmain\u002Fcontainer\u002Fcc-switch-skills\u002Fkarpathy-guidelines\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M75WYE09NJ4SP850F7J29Z37","grilling","Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.","https:\u002F\u002Fgithub.com\u002FWifabric\u002FAISC\u002Fblob\u002Fmain\u002Fcontainer\u002Fcc-switch-skills\u002Fgrilling\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FWifabric\u002FAISC\u002Fblob\u002Fmain\u002Fcontainer\u002Fcc-switch-skills\u002Fgrilling\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M75WYC9X05NCDDTYVGB7S0WN","grill-me","A relentless one-question-at-a-time interview to sharpen a plan, decision, or design.","https:\u002F\u002Fgithub.com\u002FWifabric\u002FAISC\u002Fblob\u002Fmain\u002Fcontainer\u002Fcc-switch-skills\u002Fgrill-me\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FWifabric\u002FAISC\u002Fblob\u002Fmain\u002Fcontainer\u002Fcc-switch-skills\u002Fgrill-me\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M75WYAC1WNGS5J0VYSXNG591","document-skills","Create and edit documents, spreadsheets, presentations, PDFs, and other business artifacts using the bundled Anthropic document skills.","https:\u002F\u002Fgithub.com\u002FWifabric\u002FAISC\u002Fblob\u002Fmain\u002Fcontainer\u002Fcc-switch-skills\u002Fdocument-skills\u002FSKILL.md",[],[]]