[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M698QD7RVXZTR72735TA9VTK":3,"skill-same:01M698QD7RVXZTR72735TA9VTK":88},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":59,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M698QD7RVXZTR72735TA9VTK","hanselman-code-review",null,"Adversarial dual-model code review that runs two AI models in parallel, cross-references findings, and produces a consensus severity table with fix confidence ratings. Use when asked for a thorough code review, adversarial review, dual-model review, confidence-rated review, or 'Hanselman review'.","openclaw\u002Fopenclaw-windows-node","openclaw","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F252820863?v=4","01M698P3FSAZ6B4R928ZF19KPT","01M698Q6SND6RHZDPP8ZM0NSP7",2198,"MIT","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhanselman-code-review\u002FLICENSE.md","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhanselman-code-review\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"hanselman code review","review","code review","code","when","adversarial","ratings","for","with","ai models","references","models","use","fix","consensus","parallel","model","table","severity","adversarial review","2026-11-10 10:12:30",false,"---\nname: hanselman-code-review\ndescription: \"Adversarial dual-model code review that runs two AI models in parallel, cross-references findings, and produces a consensus severity table with fix confidence ratings. Use when asked for a thorough code review, adversarial review, dual-model review, confidence-rated review, or 'Hanselman review'.\"\n---\n\n# Hanselman Adversarial Code Review Skill\n\nRun a rigorous, adversarial code review using two AI models in parallel.\nCross-reference their findings to separate signal from noise, producing a\nconsensus severity table with fix confidence ratings.\n\n## When to Use\n\nInvoke this skill when the user asks for:\n\n- A thorough or deep code review\n- An adversarial review\n- A dual-model review\n- A \"Hanselman review\"\n- A confidence-rated review\n- Cross-model validation of code changes\n\n## Philosophy\n\nSingle-model reviews have blind spots. Two models reviewing independently\nsurface different classes of issues: security, correctness, and edge cases.\nCross-reference their findings:\n\n- **HIGH consensus** (both models flag it): strong evidence; verify the issue.\n- **LOW consensus** (only one model flags it): may be noise; use judgment.\n- **Disputed** (a model flags it but evidence contradicts it): investigate\n  before acting.\n\n## Review Workflow\n\n### Step 1: Identify the Scope\n\nDetermine what code to review:\n\n- If the user specifies files, use those.\n- If the user says \"review my changes\", use `git diff` or `git diff --staged`.\n- For a PR, use `gh pr view` and `gh pr diff`, pinning the exact head and base.\n- For a branch, diff against the base branch.\n\nCapture the exact reviewed head and base before building the reviewer prompt.\nAfter both reviews finish, re-read the live head. If it changed, mark the\nreview stale and rerun both reviewers on the new revision rather than copying\nthe old verdict forward.\n\nFor a repeat review, compare the current head with the previously reviewed\nhead. Review changed code, affected callers\u002Ftests, and unresolved or disputed\nfindings rather than automatically repeating the full review. If the code is\nunchanged and only the models changed, focus both reviewers on those findings\nand high-risk decisions. State the delta scope and retain missing runtime-proof\ngates.\n\n### Step 2: Launch Two Parallel Reviews\n\nLaunch two `rubber-duck` agents via the app-native `task` tool in **background**\nmode with different models. No standalone model CLI is required.\n\n**Agent 1: Claude Opus 5.5**\n\n```javascript\ntask({\n  name: \"opus-review\",\n  agent_type: \"rubber-duck\",\n  mode: \"background\",\n  model: \"claude-opus-5.5\",\n  reasoning_effort: \"high\",\n  prompt: \"\u003Cfull context + code + review instructions>\"\n})\n```\n\n**Agent 2: GPT-6 Astra**\n\n```javascript\ntask({\n  name: \"astra-review\",\n  agent_type: \"rubber-duck\",\n  mode: \"background\",\n  model: \"gpt-6-astra\",\n  context_tier: \"long_context\",\n  reasoning_effort: \"high\",\n  prompt: \"\u003Csame context + code + review instructions>\"\n})\n```\n\nBoth agents receive the **exact same prompt** so findings are comparable.\nInclude the full file contents or diff, project context, exact revisions,\nconstraints, and the severity definitions below.\n\n### Step 3: Wait for Both to Complete\n\nUse the background interval for independent work. Wait for each completion\nnotification, then read its result with `read_agent`; do not poll. Reconcile\nboth completed reviews before publishing a consensus.\n\nA completed Hanselman review requires valid output from both requested models\non the same revision. If either reviewer fails, is unavailable, or returns an\nincomplete assessment, report the review as incomplete. Preserve any completed\noutput as advisory evidence, but do not build a consensus table or substitute a\ndifferent model without the user's approval.\n\n### Step 4: Cross-Reference and Build the Consensus Table\n\nCreate a SQL table to track findings:\n\n```sql\nCREATE TABLE IF NOT EXISTS review_findings (\n    id TEXT PRIMARY KEY,\n    issue TEXT NOT NULL,\n    opus_severity TEXT,\n    astra_severity TEXT,\n    consensus TEXT NOT NULL,\n    fix_confidence INTEGER NOT NULL\n);\n```\n\nIf the session already has a findings table, inspect and reuse or migrate its\nschema without discarding earlier findings. Record the actual model ID that\nproduced each review; do not relabel earlier findings as results from a\ndifferent model.\n\nFor each finding:\n\n1. Check whether the other model found the same or a similar issue.\n2. Assign consensus: both flagged it is `HIGH`; one flagged it is `LOW`;\n   evidence contradicting a finding is `LOW (disputed)`.\n3. Verify it against the actual code, dependency contract, and tests.\n4. Assign fix confidence:\n   - 99%: trivial fix, such as a wrong flag or missing null check.\n   - 90-95%: straightforward fix requiring some design thought.\n   - 70-80%: complex fix requiring research or trade-offs.\n   - Below 70%: hard problem, intentional behavior, or architecture change.\n\n### Step 5: Present the Results\n\nState the exact reviewed head and base, actual model IDs, context tiers, and\nreasoning effort before the finding tables. Do not describe an incomplete or\nstale run as clean.\n\n**Both Models Agree: HIGH consensus**\n\n| Issue | Opus 5.5 | GPT-6 Astra | Fix Confidence |\n|-------|----------|-------------|----------------|\n| Description of issue | SEVERITY | SEVERITY | XX% |\n\n**Only One Model Flagged: LOW consensus**\n\n| Issue | Opus 5.5 | GPT-6 Astra | Fix Confidence |\n|-------|----------|-------------|----------------|\n| Description of issue | SEVERITY or not flagged | SEVERITY or not flagged | XX% |\n\nUse `not flagged` when a model did not identify the issue.\n\n### Step 6: Act on Findings\n\n- Ask which findings to fix unless the user has already authorized the fixes.\n- Prioritize verified HIGH consensus issues.\n- Explain one-model and disputed findings before acting.\n- Do not broaden the task to satisfy a reviewer. Preserve the repository's\n  scope and proof requirements.\n- Fix confidence is the coordinator's assessment, not a model vote or a\n  replacement for runtime proof.\n\n## Review Instructions Template\n\nGive both reviewers the same adapted prompt:\n\n```text\nReview the following code changes for [PROJECT NAME].\nThis is a [LANGUAGE\u002FFRAMEWORK] project with these constraints: [CONSTRAINTS].\nExact head: [HEAD]. Base or previously reviewed head: [BASE].\n\nFocus on bugs, security issues, race conditions, and correctness problems.\nIgnore style and formatting.\nWrite every review comment in simplified technical English. Use short sentences\nand common words, explain necessary technical terms, and avoid jargon or\nunnecessary detail.\n\n[FULL CODE OR DIFF HERE]\n\nFor each issue found, classify severity as:\n- CRITICAL: will crash, corrupt data, or create a security vulnerability\n- HIGH: likely bug that will manifest in real use\n- MEDIUM: edge case that could bite in specific scenarios\n- LOW: minor improvement, theoretical concern, or robustness enhancement\n\nFor each issue, include:\n1. What the issue is\n2. Where it is (file and line\u002Fregion)\n3. Why it matters (impact and reachability)\n4. Suggested fix\n```\n\n## Model Selection\n\nThe default pairing is **Claude Opus 5.5** (`claude-opus-5.5`) and\n**GPT-6 Astra** (`gpt-6-astra`, `context_tier: \"long_context\"`), both with\n`reasoning_effort: \"high\"`. Different model families provide independent\nperspectives on the same evidence.\n\nUse the tool's supported `long_context` value, not an invented model name or\nmodel-name suffix. Do not assume a numeric context-window size. Preserve the\nhigh reasoning default unless the user requests a different effort.\n\nIf a preferred model or context tier is unavailable, report the limitation and\nuse an available alternative only with the user's approval. Record the actual\nmodel IDs and context tiers used; do not silently fall back to an older\ngeneration.\n\n## Important Notes\n\n- Never skip cross-referencing. The value is in the comparison, not individual\n  reviews.\n- Both requested reviewers must complete on the same exact revision. One valid\n  review plus one failure is not a dual-model verdict.\n- Log disputed findings and the reasoning for accepting or rejecting them.\n- Model output is advisory input. Verify every accepted finding against the\n  actual code, tests, and dependency behavior before acting.\n- Do not fix LOW consensus issues without user authorization.\n- A clean source review does not satisfy a missing Windows proof pool,\n  current-head UI proof, or required CI check.\n","# Hanselman Adversarial Code Review Skill\n\nRun a rigorous, adversarial code review using two AI models in parallel.\nCross-reference their findings to separate signal from noise, producing a\nconsensus severity table with fix confidence ratings.\n\n## When to Use\n\nInvoke this skill when the user asks for:\n\n- A thorough or deep code review\n- An adversarial review\n- A dual-model review\n- A \"Hanselman review\"\n- A confidence-rated review\n- Cross-model validation of code changes\n\n## Philosophy\n\nSingle-model reviews have blind spots. Two models reviewing independently\nsurface different classes of issues: security, correctness, and edge cases.\nCross-reference their findings:\n\n- **HIGH consensus** (both models flag it): strong evidence; verify the issue.\n- **LOW consensus** (only one model flags it): may be noise; use judgment.\n- **Disputed** (a model flags it but evidence contradicts it): investigate\n  before acting.\n\n## Review Workflow\n\n### Step 1: Identify the Scope\n\nDetermine what code to review:\n\n- If the user specifies files, use those.\n- If the user says \"review my changes\", use `git diff` or `git diff --staged`.\n- For a PR, use `gh pr view` and `gh pr diff`, pinning the exact head and base.\n- For a branch, diff against the base branch.\n\nCapture the exact reviewed head and base before building the reviewer prompt.\nAfter both reviews finish, re-read the live head. If it changed, mark the\nreview stale and rerun both reviewers on the new revision rather than copying\nthe old verdict forward.\n\nFor a repeat review, compare the current head with the previously reviewed\nhead. Review changed code, affected callers\u002Ftests, and unresolved or disputed\nfindings rather than automatically repeating the full review. If the code is\nunchanged and only the models changed, focus both reviewers on those findings\nand high-risk decisions. State the delta scope and retain missing runtime-proof\ngates.\n\n### Step 2: Launch Two Parallel Reviews\n\nLaunch two `rubber-duck` agents via the app-native `task` tool in **background**\nmode with different models. No standalone model CLI is required.\n\n**Agent 1: Claude Opus 5.5**\n\n```javascript\ntask({\n  name: \"opus-review\",\n  agent_type: \"rubber-duck\",\n  mode: \"background\",\n  model: \"claude-opus-5.5\",\n  reasoning_effort: \"high\",\n  prompt: \"\u003Cfull context + code + review instructions>\"\n})\n```\n\n**Agent 2: GPT-6 Astra**\n\n```javascript\ntask({\n  name: \"astra-review\",\n  agent_type: \"rubber-duck\",\n  mode: \"background\",\n  model: \"gpt-6-astra\",\n  context_tier: \"long_context\",\n  reasoning_effort: \"high\",\n  prompt: \"\u003Csame context + code + review instructions>\"\n})\n```\n\nBoth agents receive the **exact same prompt** so findings are comparable.\nInclude the full file contents or diff, project context, exact revisions,\nconstraints, and the severity definitions below.\n\n### Step 3: Wait for Both to Complete\n\nUse the background interval for independent work. Wait for each completion\nnotification, then read its result with `read_agent`; do not poll. Reconcile\nboth completed reviews before publishing a consensus.\n\nA completed Hanselman review requires valid output from both requested models\non the same revision. If either reviewer fails, is unavailable, or returns an\nincomplete assessment, report the review as incomplete. Preserve any completed\noutput as advisory evidence, but do not build a consensus table or substitute a\ndifferent model without the user's approval.\n\n### Step 4: Cross-Reference and Build the Consensus Table\n\nCreate a SQL table to track findings:\n\n```sql\nCREATE TABLE IF NOT EXISTS review_findings (\n    id TEXT PRIMARY KEY,\n    issue TEXT NOT NULL,\n    opus_severity TEXT,\n    astra_severity TEXT,\n    consensus TEXT NOT NULL,\n    fix_confidence INTEGER NOT NULL\n);\n```\n\nIf the session already has a findings table, inspect and reuse or migrate its\nschema without discarding earlier findings. Record the actual model ID that\nproduced each review; do not relabel earlier findings as results from a\ndifferent model.\n\nFor each finding:\n\n1. Check whether the other model found the same or a similar issue.\n2. Assign consensus: both flagged it is `HIGH`; one flagged it is `LOW`;\n   evidence contradicting a finding is `LOW (disputed)`.\n3. Verify it against the actual code, dependency contract, and tests.\n4. Assign fix confidence:\n   - 99%: trivial fix, such as a wrong flag or missing null check.\n   - 90-95%: straightforward fix requiring some design thought.\n   - 70-80%: complex fix requiring research or trade-offs.\n   - Below 70%: hard problem, intentional behavior, or architecture change.\n\n### Step 5: Present the Results\n\nState the exact reviewed head and base, actual model IDs, context tiers, and\nreasoning effort before the finding tables. Do not describe an incomplete or\nstale run as clean.\n\n**Both Models Agree: HIGH consensus**\n\n| Issue | Opus 5.5 | GPT-6 Astra | Fix Confidence |\n|-------|----------|-------------|----------------|\n| Description of issue | SEVERITY | SEVERITY | XX% |\n\n**Only One Model Flagged: LOW consensus**\n\n| Issue | Opus 5.5 | GPT-6 Astra | Fix Confidence |\n|-------|----------|-------------|----------------|\n| Description of issue | SEVERITY or not flagged | SEVERITY or not flagged | XX% |\n\nUse `not flagged` when a model did not identify the issue.\n\n### Step 6: Act on Findings\n\n- Ask which findings to fix unless the user has already authorized the fixes.\n- Prioritize verified HIGH consensus issues.\n- Explain one-model and disputed findings before acting.\n- Do not broaden the task to satisfy a reviewer. Preserve the repository's\n  scope and proof requirements.\n- Fix confidence is the coordinator's assessment, not a model vote or a\n  replacement for runtime proof.\n\n## Review Instructions Template\n\nGive both reviewers the same adapted prompt:\n\n```text\nReview the following code changes for [PROJECT NAME].\nThis is a [LANGUAGE\u002FFRAMEWORK] project with these constraints: [CONSTRAINTS].\nExact head: [HEAD]. Base or previously reviewed head: [BASE].\n\nFocus on bugs, security issues, race conditions, and correctness problems.\nIgnore style and formatting.\nWrite every review comment in simplified technical English. Use short sentences\nand common words, explain necessary technical terms, and avoid jargon or\nunnecessary detail.\n\n[FULL CODE OR DIFF HERE]\n\nFor each issue found, classify severity as:\n- CRITICAL: will crash, corrupt data, or create a security vulnerability\n- HIGH: likely bug that will manifest in real use\n- MEDIUM: edge case that could bite in specific scenarios\n- LOW: minor improvement, theoretical concern, or robustness enhancement\n\nFor each issue, include:\n1. What the issue is\n2. Where it is (file and line\u002Fregion)\n3. Why it matters (impact and reachability)\n4. Suggested fix\n```\n\n## Model Selection\n\nThe default pairing is **Claude Opus 5.5** (`claude-opus-5.5`) and\n**GPT-6 Astra** (`gpt-6-astra`, `context_tier: \"long_context\"`), both with\n`reasoning_effort: \"high\"`. Different model families provide independent\nperspectives on the same evidence.\n\nUse the tool's supported `long_context` value, not an invented model name or\nmodel-name suffix. Do not assume a numeric context-window size. Preserve the\nhigh reasoning default unless the user requests a different effort.\n\nIf a preferred model or context tier is unavailable, report the limitation and\nuse an available alternative only with the user's approval. Record the actual\nmodel IDs and context tiers used; do not silently fall back to an older\ngeneration.\n\n## Important Notes\n\n- Never skip cross-referencing. The value is in the comparison, not individual\n  reviews.\n- Both requested reviewers must complete on the same exact revision. One valid\n  review plus one failure is not a dual-model verdict.\n- Log disputed findings and the reasoning for accepting or rejecting them.\n- Model output is advisory input. Verify every accepted finding against the\n  actual code, tests, and dependency behavior before acting.\n- Do not fix LOW consensus issues without user authorization.\n- A clean source review does not satisfy a missing Windows proof pool,\n  current-head UI proof, or required CI check.\n",{"name":5,"description":7},"main","a4dd026cc5f85a444a0fcd05eef5b86282dbda8c",".agents\u002Fskills\u002Fhanselman-code-review",349,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node","https:\u002F\u002Fopenclaw.ai","https:\u002F\u002Fgithub.com\u002Fopenclaw","Your personal, open source AI assistant.","2026-11-14 18:13:49",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add openclaw\u002Fopenclaw-windows-node --skill hanselman-code-review",{"tool":69,"command":70},"bunx","bunx skills add openclaw\u002Fopenclaw-windows-node --skill hanselman-code-review",{"tool":72,"command":73},"pnpm","pnpm dlx skills add openclaw\u002Fopenclaw-windows-node --skill hanselman-code-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhanselman-code-review\u002FSKILL.md",true,[77,82],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":15},"LICENSE.md","LICENSE","许可证",1072,{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"README.md","REFERENCE","参考文档",2186,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhanselman-code-review\u002FREADME.md",[89,97,119,137,155,174],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":96},"01M7416EHCYH7YCJ9XPSQ2844V","network-handoff","Use before generating, changing, or reviewing networking, IPC, or cross-process handoffs, including requests, retries, deadlines, reconnect, process launch, configuration apply, cancellation, and cleanup. Establish confirmation, identity, authority, reconciliation, and producer compatibility before implementation.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fnetwork-handoff\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":49},"01M6KZCXK5PCYWWW5FCVDYPAXK","retrigger-flaky-ci","Triage failed CI on a pull request or the active branch, decide whether the failures come from its changes, and rerun only failures that are unrelated. Use when asked to retrigger, rerun, or kick CI on a PR with failing checks.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fretrigger-flaky-ci\u002FSKILL.md",[],[104,105,33,106,107,108,41,109,110,111,112,113,114,115,116,117,37,118],"retrigger flaky ci","ci","pull request","failing","rerun","triage","only","decide","request","active","pr","changes","unrelated","branch","pull",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":49},"01M698QMQN5TQES4R7ZPTYAZF5","technical-documentation","Write, review, or restructure Windows node documentation and agent instructions using current source, task-focused explanations, and explicit fact preservation.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftechnical-documentation\u002FSKILL.md",[],[126,127,128,129,130,30,131,132,133,134,135,136],"technical","documentation","technical documentation","node","instructions","write","task","windows","agent instructions","preservation","source",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":49},"01M698QKPXJ8ZG34MYHPPCAT4T","pr-simplify","Simplify your own Windows-node change to its smallest complete fix while preserving distinct regressions, platform contracts, and required proof. Use after implementation before PR preparation, after large repairs, or when asked to shrink a change or remove slop.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpr-simplify\u002FSKILL.md",[],[144,114,145,146,147,148,149,133,150,33,41,42,151,152,153,154,129],"pr simplify","simplify","preparation","contracts","proof","implementation","change","complete","remove","slop","platform",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":164,"publishedAt":49},"01M698QJEA384YPM8R9CPZ1YFD","openclaw-testing","Choose proportional OpenClaw Windows node tests, builds, packaging checks, and runtime proof, then diagnose failures without weakening required gates.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fopenclaw-testing\u002FSKILL.md",[161],{"categoryNo":162,"categoryName":163,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[9,165,166,167,133,168,148,129,169,170,171,172,173],"openclaw testing","testing","diagnose","runtime","gates","runtime proof","tests","choose","packaging",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":183,"publishedAt":49},"01M698QH7JVVA09769ER9P2TKY","openclaw-proof-validation","Plan and collect OpenClaw Windows validation\u002Fproof: tests, rubber-duck review, UI evidence, MCP output, and gateway runtime proof.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fopenclaw-proof-validation\u002FSKILL.md",[180],{"categoryNo":181,"categoryName":182,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[148,184,185,9,170,186,187,188,189,190,30,171,191,168,192,133,193,194],"validation","openclaw proof validation","duck","ui","ui evidence","plan","output","collect","evidence","gateway","MCP"]