[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KJACNV1SK2F4VYPB2CK8K6":3,"skill-same:01M6KJACNV1SK2F4VYPB2CK8K6":69},{"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":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":13,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6KJACNV1SK2F4VYPB2CK8K6","caveman-review",null,"Ultra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says \"review this PR\", \"code review\", \"review the diff\", \"\u002Freview\", or invokes \u002Fcaveman-review. Auto-triggers when reviewing pull requests.","nposadaa\u002Fwa_trm_notifier","nposadaa","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F57275210?v=4","01M6KJ95HX8AHGQ83PJKSD5HTE","01M6KJ95NTKE2PHAY9Z88HFXYS",0,"MIT","https:\u002F\u002Fgithub.com\u002Fnposadaa\u002Fwa_trm_notifier\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fcaveman\u002Fskills\u002Fcaveman-review\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"review","caveman","caveman review","requests","code review","comments","actionable","problem","line","triggers","auto","diff","use","fix","feedback","pr feedback","pull","code","pr","pull requests","2026-11-10 10:12:30",false,"---\nname: caveman-review\ndescription: >\n  Ultra-compressed code review comments. Cuts noise from PR feedback while preserving\n  the actionable signal. Each comment is one line: location, problem, fix. Use when user\n  says \"review this PR\", \"code review\", \"review the diff\", \"\u002Freview\", or invokes\n  \u002Fcaveman-review. Auto-triggers when reviewing pull requests.\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},"master","afd8a0f0dcb9b77a6380674baf34aac507e69d70",".agents\u002Fskills\u002Fcaveman\u002Fskills\u002Fcaveman-review","https:\u002F\u002Fgithub.com\u002Fnposadaa\u002Fwa_trm_notifier","https:\u002F\u002Fgithub.com\u002Fnposadaa","Fun = Nerdism + Technology","2026-11-05 00:20:35",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add nposadaa\u002Fwa_trm_notifier --skill caveman-review",{"tool":61,"command":62},"bunx","bunx skills add nposadaa\u002Fwa_trm_notifier --skill caveman-review",{"tool":64,"command":65},"pnpm","pnpm dlx skills add nposadaa\u002Fwa_trm_notifier --skill caveman-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnposadaa\u002Fwa_trm_notifier\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fcaveman\u002Fskills\u002Fcaveman-review\u002FSKILL.md",true,[],[70,83,101,115,127,141],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":43},"01M6KJD0BT88C4KVQ7RJJTPT7Y","verifier","Validates implemented work against spec requirements with empirical evidence","https:\u002F\u002Fgithub.com\u002Fnposadaa\u002Fwa_trm_notifier\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fverifier\u002FSKILL.md",[],[72,77,78,79,80,81,82],"spec","work","evidence","requirements","spec requirements","with",{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":94,"publishedAt":43},"01M6KJCTEPAAPV3YE6GXFC1RQ4","token-budget","Manages token budget estimation and tracking to prevent context overflow","https:\u002F\u002Fgithub.com\u002Fnposadaa\u002Fwa_trm_notifier\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Ftoken-budget\u002FSKILL.md",[89],{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000040","财务","PROFESSION","适用职业",[95,96,97,98,99,100],"token budget","token","Budget","context","tracking","estimation",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":43},"01M6KJCN162BN1C6P66K52TZVP","planner","Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification","https:\u002F\u002Fgithub.com\u002Fnposadaa\u002Fwa_trm_notifier\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fplanner\u002FSKILL.md",[],[103,108,109,82,110,111,112,113,114],"task","plans","dependency analysis","goal","verification","analysis","dependency",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":43},"01M6KJCHHQ3HNHDH8DAEJN3JDC","plan-checker","Validates plans before execution to catch issues early","https:\u002F\u002Fgithub.com\u002Fnposadaa\u002Fwa_trm_notifier\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fplan-checker\u002FSKILL.md",[],[122,123,124,125,126,109],"checker","plan checker","plan","execution","issues",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":43},"01M6KJCDQS4C0DSVZ52CW053MJ","status","Show MemPalace status — room counts, storage usage, and palace health.","https:\u002F\u002Fgithub.com\u002Fnposadaa\u002Fwa_trm_notifier\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fmempalace\u002F.codex-plugin\u002Fskills\u002Fstatus\u002FSKILL.md",[],[129,134,135,136,137,138,139,140],"health","Bash","read","show","mempalace","usage","storage",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":43},"01M6KJCA2PFKKNEFZWMMTE3XHM","search","Search your MemPalace — semantic search across all mined memories, projects, and conversations.","https:\u002F\u002Fgithub.com\u002Fnposadaa\u002Fwa_trm_notifier\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fmempalace\u002F.codex-plugin\u002Fskills\u002Fsearch\u002FSKILL.md",[],[143,148,136,135,149,150,151,138,152,153],"projects","semantic search","conversations","semantic","memories","across"]