[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71R12AS9R11SPPDKHDKHPSN":3,"skill-same:01M71R12AS9R11SPPDKHDKHPSN":64},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M71R12AS9R11SPPDKHDKHPSN","bmad-review-edge-case-hunter",null,"Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven. Use when you need exhaustive edge-case analysis of code, specs, or diffs.","developAgent\u002Fbmad-start","developAgent","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F264530239?v=4","01M71J8X6CY24V5ZZHFGETRMSW","01M71J8X739FS28DGQAAY7V4QR",1,"MIT","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.rovodev\u002Fskills\u002Fbmad-review-edge-case-hunter\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"edge","bmad","review","case","bmad review edge case","bmad review","bmad review edge case hunter","hunter","adversarial review","report","adversarial","boundary","code","analysis","you","when","use","only","diffs","condition","2026-11-10 13:02:02",false,"---\nname: bmad-review-edge-case-hunter\ndescription: 'Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven. Use when you need exhaustive edge-case analysis of code, specs, or diffs.'\n---\n\n# Edge Case Hunter Review\n\n**Goal:** You are a pure path tracer. Never comment on whether code is good or bad; only list missing handling.\nWhen a diff is provided, scan only the diff hunks and list boundaries that are directly reachable from the changed lines and lack an explicit guard in the diff.\nWhen no diff is provided (full file or function), treat the entire provided content as the scope.\nIgnore the rest of the codebase unless the provided content explicitly references external functions.\n\n**Inputs:**\n- **content** — Content to review: diff, full file, or function\n- **also_consider** (optional) — Areas to keep in mind during review alongside normal edge-case analysis\n\n**MANDATORY: Execute steps in the Execution section IN EXACT ORDER. DO NOT skip steps or change the sequence. When a halt condition triggers, follow its specific instruction exactly. Each action within a step is a REQUIRED action to complete that step.**\n\n**Your method is exhaustive path enumeration — mechanically walk every branch, not hunt by intuition. Report ONLY paths and conditions that lack handling — discard handled ones silently. Do NOT editorialize or add filler — findings only.**\n\n\n## EXECUTION\n\n### Step 1: Receive Content\n\n- Load the content to review strictly from provided input\n- If content is empty, or cannot be decoded as text, return `[{\"location\":\"N\u002FA\",\"trigger_condition\":\"Input empty or undecodable\",\"guard_snippet\":\"Provide valid content to review\",\"potential_consequence\":\"Review skipped — no analysis performed\"}]` and stop\n- Identify content type (diff, full file, or function) to determine scope rules\n\n### Step 2: Exhaustive Path Analysis\n\n**Walk every branching path and boundary condition within scope — report only unhandled ones.**\n\n- If `also_consider` input was provided, incorporate those areas into the analysis\n- Walk all branching paths: control flow (conditionals, loops, error handlers, early returns) and domain boundaries (where values, states, or conditions transition). Derive the relevant edge classes from the content itself — don't rely on a fixed checklist. Examples: missing else\u002Fdefault, unguarded inputs, off-by-one loops, arithmetic overflow, implicit type coercion, race conditions, timeout gaps\n- For each path: determine whether the content handles it\n- Collect only the unhandled paths as findings — discard handled ones silently\n\n### Step 3: Validate Completeness\n\n- Revisit every edge class from Step 2 — e.g., missing else\u002Fdefault, null\u002Fempty inputs, off-by-one loops, arithmetic overflow, implicit type coercion, race conditions, timeout gaps\n- Add any newly found unhandled paths to findings; discard confirmed-handled ones\n\n### Step 4: Present Findings\n\nOutput findings as a JSON array following the Output Format specification exactly.\n\n\n## OUTPUT FORMAT\n\nReturn ONLY a valid JSON array of objects. Each object must contain exactly these four fields and nothing else:\n\n```json\n[{\n  \"location\": \"file:start-end (or file:line when single line, or file:hunk when exact line unavailable)\",\n  \"trigger_condition\": \"one-line description (max 15 words)\",\n  \"guard_snippet\": \"minimal code sketch that closes the gap (single-line escaped string, no raw newlines or unescaped quotes)\",\n  \"potential_consequence\": \"what could actually go wrong (max 15 words)\"\n}]\n```\n\nNo extra text, no explanations, no markdown wrapping. An empty array `[]` is valid when no unhandled paths are found.\n\n\n## HALT CONDITIONS\n\n- If content is empty or cannot be decoded as text, return `[{\"location\":\"N\u002FA\",\"trigger_condition\":\"Input empty or undecodable\",\"guard_snippet\":\"Provide valid content to review\",\"potential_consequence\":\"Review skipped — no analysis performed\"}]` and stop\n","# Edge Case Hunter Review\n\n**Goal:** You are a pure path tracer. Never comment on whether code is good or bad; only list missing handling.\nWhen a diff is provided, scan only the diff hunks and list boundaries that are directly reachable from the changed lines and lack an explicit guard in the diff.\nWhen no diff is provided (full file or function), treat the entire provided content as the scope.\nIgnore the rest of the codebase unless the provided content explicitly references external functions.\n\n**Inputs:**\n- **content** — Content to review: diff, full file, or function\n- **also_consider** (optional) — Areas to keep in mind during review alongside normal edge-case analysis\n\n**MANDATORY: Execute steps in the Execution section IN EXACT ORDER. DO NOT skip steps or change the sequence. When a halt condition triggers, follow its specific instruction exactly. Each action within a step is a REQUIRED action to complete that step.**\n\n**Your method is exhaustive path enumeration — mechanically walk every branch, not hunt by intuition. Report ONLY paths and conditions that lack handling — discard handled ones silently. Do NOT editorialize or add filler — findings only.**\n\n\n## EXECUTION\n\n### Step 1: Receive Content\n\n- Load the content to review strictly from provided input\n- If content is empty, or cannot be decoded as text, return `[{\"location\":\"N\u002FA\",\"trigger_condition\":\"Input empty or undecodable\",\"guard_snippet\":\"Provide valid content to review\",\"potential_consequence\":\"Review skipped — no analysis performed\"}]` and stop\n- Identify content type (diff, full file, or function) to determine scope rules\n\n### Step 2: Exhaustive Path Analysis\n\n**Walk every branching path and boundary condition within scope — report only unhandled ones.**\n\n- If `also_consider` input was provided, incorporate those areas into the analysis\n- Walk all branching paths: control flow (conditionals, loops, error handlers, early returns) and domain boundaries (where values, states, or conditions transition). Derive the relevant edge classes from the content itself — don't rely on a fixed checklist. Examples: missing else\u002Fdefault, unguarded inputs, off-by-one loops, arithmetic overflow, implicit type coercion, race conditions, timeout gaps\n- For each path: determine whether the content handles it\n- Collect only the unhandled paths as findings — discard handled ones silently\n\n### Step 3: Validate Completeness\n\n- Revisit every edge class from Step 2 — e.g., missing else\u002Fdefault, null\u002Fempty inputs, off-by-one loops, arithmetic overflow, implicit type coercion, race conditions, timeout gaps\n- Add any newly found unhandled paths to findings; discard confirmed-handled ones\n\n### Step 4: Present Findings\n\nOutput findings as a JSON array following the Output Format specification exactly.\n\n\n## OUTPUT FORMAT\n\nReturn ONLY a valid JSON array of objects. Each object must contain exactly these four fields and nothing else:\n\n```json\n[{\n  \"location\": \"file:start-end (or file:line when single line, or file:hunk when exact line unavailable)\",\n  \"trigger_condition\": \"one-line description (max 15 words)\",\n  \"guard_snippet\": \"minimal code sketch that closes the gap (single-line escaped string, no raw newlines or unescaped quotes)\",\n  \"potential_consequence\": \"what could actually go wrong (max 15 words)\"\n}]\n```\n\nNo extra text, no explanations, no markdown wrapping. An empty array `[]` is valid when no unhandled paths are found.\n\n\n## HALT CONDITIONS\n\n- If content is empty or cannot be decoded as text, return `[{\"location\":\"N\u002FA\",\"trigger_condition\":\"Input empty or undecodable\",\"guard_snippet\":\"Provide valid content to review\",\"potential_consequence\":\"Review skipped — no analysis performed\"}]` and stop\n",{"name":5,"description":7},"main","1907bbe850fb749efa8b499b8da7ebb78a663519",".rovodev\u002Fskills\u002Fbmad-review-edge-case-hunter",0,"https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start","https:\u002F\u002Fgithub.com\u002FdevelopAgent","2026-07-19 05:19:22",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add developAgent\u002Fbmad-start --skill bmad-review-edge-case-hunter",{"tool":56,"command":57},"bunx","bunx skills add developAgent\u002Fbmad-start --skill bmad-review-edge-case-hunter",{"tool":59,"command":60},"pnpm","pnpm dlx skills add developAgent\u002Fbmad-start --skill bmad-review-edge-case-hunter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.rovodev\u002Fskills\u002Fbmad-review-edge-case-hunter\u002FSKILL.md",true,[],[65,86,113,131,145,171],{"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":76,"publishedAt":38},"01M71R3M9DJTTY0ARFQ6K04NMP","gds-correct-course","Manage significant changes during sprint execution. Use when the user says \"correct course\" or \"propose sprint change\"","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.rovodev\u002Fskills\u002Fgds-correct-course\u002FSKILL.md",[71],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000039","教师与教育","PROFESSION","适用职业",[77,78,79,80,81,82,33,34,83,84,85],"gds correct course","course","correct","user","changes","change","execution","manage","sprint",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":100,"publishedAt":38},"01M71R3GENSFD1A1XVZTTQG1KF","gds-code-review","Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says \"run code review\" or \"review this code\"","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.rovodev\u002Fskills\u002Fgds-code-review\u002FSKILL.md",[92,97],{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":98,"categoryName":99,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000030","开发工程师",[101,30,20,102,103,81,104,105,106,107,21,108,109,33,110,34,18,111,112,25],"code review","gds code review","categories","triage","review code","run","parallel","with","run code","acceptance","actionable","layers",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":38},"01M71R3DD098MQRD6F8S4GG0AW","gds-check-implementation-readiness","Verify GDD, UX, Architecture, and Epics alignment before production. Use when the user says \"check readiness\" or \"implementation readiness\"","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.rovodev\u002Fskills\u002Fgds-check-implementation-readiness\u002FSKILL.md",[],[120,121,122,123,124,125,80,126,127,128,129,33,34,130],"check","readiness","Implementation Readiness","gds check implementation readiness","implementation","check readiness","Production","ux","verify","architecture","alignment",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":38},"01M71R3ACAA1G0NVQ330JQNJPK","gds-brainstorm-game","Facilitate game brainstorming sessions with game-specific techniques. Use when the user says \"brainstorm game\" or \"game ideas\"","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.rovodev\u002Fskills\u002Fgds-brainstorm-game\u002FSKILL.md",[],[138,139,140,80,141,108,33,34,142,143,144],"gds brainstorm game","game","brainstorm","brainstorming","techniques","sessions","ideas",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":154,"publishedAt":38},"01M71R377MJ6WJTTFARGKH3HX7","gds-agent-tech-writer","Technical documentation specialist and knowledge curator for game projects. Use when the user asks to talk to Paige or requests the Technical Writer.","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.rovodev\u002Fskills\u002Fgds-agent-tech-writer\u002FSKILL.md",[151],{"categoryNo":152,"categoryName":153,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000023","Skill与智能体开发",[155,156,157,158,34,159,160,161,162,33,80,163,164,165,166,167,168,169,139,170],"gds agent tech writer","tech","writer","technical writer","technical","knowledge","for","projects","technical documentation","talk","specialist","documentation specialist","knowledge curator","requests","documentation","curator",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":178,"publishedAt":38},"01M71R34RGT2ZX3TSFA2CRT0NC","gds-agent-game-solo-dev","Elite indie game developer for rapid prototyping and solo quick-flow development. Use when the user asks to talk to Indie or requests the Game Solo Dev.","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.rovodev\u002Fskills\u002Fgds-agent-game-solo-dev\u002FSKILL.md",[177],{"categoryNo":152,"categoryName":153,"taxonomyType":95,"taxonomyTypeDesc":96},[179,139,180,181,182,183,80,164,168,184,185,33,34,186,161,187,188],"solo","gds agent game solo dev","dev","flow","developer","RAPID","game developer","prototyping","development","quick"]