[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71B5WSAP7A08JYBK2NVZFD1":3,"skill-same:01M71B5WSAP7A08JYBK2NVZFD1":67},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M71B5WSAP7A08JYBK2NVZFD1","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.","Wizarck\u002Fnexandro","Wizarck","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F23051550?v=4","01M71B3AAVR67GRWFV5ZXXZP31","arturo6ramirez","01M71B3ABYG1BFNXHX4KZ3PPK6",2,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fbmad-review-edge-case-hunter\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"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 10:12:30",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},"master","f57cddf3a79f076c1bb1ba9c187850fba797c0c9","skills\u002Fbmad-review-edge-case-hunter",1,"https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro","https:\u002F\u002Fgithub.com\u002FWizarck","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Framirezarturo\u002F","Geek by birth, with not much to say but plenty to talk about.","2026-09-25 20:04:26",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add Wizarck\u002Fnexandro --skill bmad-review-edge-case-hunter",{"tool":59,"command":60},"bunx","bunx skills add Wizarck\u002Fnexandro --skill bmad-review-edge-case-hunter",{"tool":62,"command":63},"pnpm","pnpm dlx skills add Wizarck\u002Fnexandro --skill bmad-review-edge-case-hunter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fbmad-review-edge-case-hunter\u002FSKILL.md",true,[],[68,102,130,153,167,193],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":84,"publishedAt":39},"01M71BBM78XJY2YXFXJ2YNCEGY","xlsx","Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file; create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files into proper spreadsheets.","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fxlsx\u002FSKILL.md",[74,79],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000004","电子表格","SCENARIO","使用场景",{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[70,85,86,87,88,89,90,91,92,93,94,95,96,35,97,34,98,99,100,101],"sources","tsv","by name","for","spreadsheet","time","trigger","fix","scratch","open","new","files","Existing","done","convert","file","tabular",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":114,"publishedAt":39},"01M71BBGZJG2FKCPJZWR32SCZ5","use-case-research","Creates JTBD-aligned Use Cases CSVs through structured user interviews, parallel vendor\u002Findustry research, and Jobs-to-be-Done synthesis. Generates 17-column CSV (OFFER-001 format) and validates with \u002Fqa-use-cases. Use when creating or updating use case research for an offering.","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fuse-case-research\u002FSKILL.md",[108,111],{"categoryNo":109,"categoryName":110,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":112,"categoryName":113,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000023","Skill与智能体开发",[115,35,22,116,117,118,119,120,34,98,121,122,123,124,125,126,127,128,88,129],"use case research","research","industry research","user interviews","qa","jtbd","Bash","websearch","read","write","edit","interviews","opus","parallel","true",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":137,"publishedAt":39},"01M71BBCCGXCBJZSYK72CT7MJW","sync-jira","Two-way sync between PROGRESS.md pipeline status and JIRA CIT tasks. Use when syncing offering progress with JIRA, checking JIRA status, bootstrapping JIRA tasks for new offerings, or pushing\u002Fpulling status updates. Also use when the user mentions JIRA, CIT tasks, or pipeline sync.","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fsync-jira\u002FSKILL.md",[136],{"categoryNo":112,"categoryName":113,"taxonomyType":77,"taxonomyTypeDesc":78},[138,139,140,141,142,88,143,144,95,145,35,34,146,121,147,148,149,150,151,152],"sync jira","jira","sync","pull","push","pipeline","status updates","MCP","updates","tasks","bootstrap","dry","two","with","id",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":160,"publishedAt":39},"01M71BBAV2F4ABBVAM9FMZ692C","strategy","Tunes business strategy and aligns with corporate ABC Goals. Use when working on 01_BS\u002F business strategy files.","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fstrategy\u002FSKILL.md",[159],{"categoryNo":112,"categoryName":113,"taxonomyType":77,"taxonomyTypeDesc":78},[155,129,96,35,161,34,151,152,162,163,123,124,125,164,165,166],"business","goals","business strategy","corporate","grep","sonnet",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":177,"publishedAt":39},"01M71BB6N1EJDAMAWAF0FSGFRR","start","Starts the full MCP stack: LiteLLM proxy + Docker services (Hindsight, Atlassian, Google Workspace) + skills-manager + notebooklm. All services connect directly — no proxy. Use \u002Fstart at the beginning of any session where MCP tools are needed, or when any service is stopped. LiteLLM must start before Docker — Hindsight depends on it at startup.","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fstart\u002FSKILL.md",[173,176],{"categoryNo":174,"categoryName":175,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":112,"categoryName":113,"taxonomyType":77,"taxonomyTypeDesc":78},[169,178,179,180,181,182,183,145,35,184,34,121,185,186,187,188,189,190,191,192],"hindsight","google workspace","proxy","docker","session","litellm","connect","stack","haiku","services","workspace","at","notebooklm","google","startup",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":200,"publishedAt":39},"01M71BB50307CW202PCTECJ3BB","start-palafito","Úsalo cuando el usuario quiere arrancar el stack palafito-prod (Paperclip) y, si hace falta, levantar Docker Desktop antes.","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fstart-palafito\u002FSKILL.md",[199],{"categoryNo":174,"categoryName":175,"taxonomyType":77,"taxonomyTypeDesc":78},[169,201,185,202,203,204,121,181,166],"start palafito","desktop","fork","paperclip"]