[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71R36S0RXAEYHHXJMQW277N":3,"skill-same:01M71R36S0RXAEYHHXJMQW277N":66},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":13,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M71R36S0RXAEYHHXJMQW277N","issue-root-resolution",null,"Trigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de raíz, close outdated issues. Audit and resolve issue clusters by verified root cause.","LuisAlbertoMK\u002Fgentleman-agent-gh","LuisAlbertoMK","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96153499?v=4","01M71QZX0CF9KKGQZ8ZN9BME63","01M71QZX11P5X6Z27HE1GQDF71",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FLuisAlbertoMK\u002Fgentleman-agent-gh\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fissue-root-resolution\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"issue root resolution","issue","resolution","root","trigger","Clusters","root cause","verified","deletion","resolver","close","de","issues","driven","map","backlog","fix","programming","audit","2026-11-10 13:02:02",false,"---\nname: issue-root-resolution\ndescription: \"Trigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de raíz, close outdated issues. Audit and resolve issue clusters by verified root cause.\"\ntriggers: \"root audit, issue roots, backlog roots, mechanism map, deletion-driven fix, close outdated issues, root cause\"\nlicense: Apache-2.0\nmetadata:\n  author: gentleman-programming\n  version: \"1.0\"\n---\n\n## Activation Contract\n\nLoad when auditing a defect backlog for shared root causes, proposing a fix for an issue cluster, or closing issues as resolved\u002Foutdated. Complements `rdd-defect-workflow` (single-defect flow) — this skill governs the cluster-level method.\n\n## Hard Rules\n\n- Read full bodies and comments, never titles. Classify against the actual code or PR diff, not descriptions of it.\n- Verify every \"fixed\" or \"broken\" claim against current `origin\u002Fmain` the day you act. Compare report dates to fix merge dates: a repro filed before the fix landed is evidence about old builds, not current code.\n- Cluster defects by causal root, not surface. Each root gets a measured row in the meta-issue (#2471 style): issues attached, fix shape, state.\n- Before proposing any fix, produce a read-only mechanism map: one file:line anchor per claim, mechanism explained as implemented today. Report claim-vs-code mismatches explicitly; never force evidence to fit the hypothesis. Let the map shrink the proposal.\n- Rank solutions by what they DELETE: (1) removes a mechanism so the class becomes impossible, (2) static guard-ratchet making reintroduction a test failure, (3) localized predicate fix behind a failing repro test. New surface (verbs, flags, mechanisms) is last resort — defer until re-verified evidence demands it.\n- Extract maintainer choices as named D-items with recommended defaults. A maintainer condition recorded in an issue thread outranks any plan table, including yours.\n- Close only with evidence, one rule per closure: (A) fixed on main, cite commit AND proving test; (B) superseded by recorded maintainer decision; (C) surface no longer exists; (D) duplicate of a fixed issue. Comment before closing: what resolved it, verified today, reopen invitation. When in doubt, do not close — list as borderline.\n- Clean break, never compatibility. When a format or identity changes, bump its versioned tag as a REPLACEMENT: old records become outdated and fail closed with an actionable refusal naming the rerun. Never write dual recognition, legacy fallbacks, or compat shims; that residue is what the deletion criterion exists to prevent. Stored bytes are never rewritten and stay readable for forensics, but carry no gate or lifecycle validity.\n- Implementation follows the waves recipe: repro as failing test first, byte-stable goldens as defect signal, independently revertible slices, one writer per slice.\n- A universal guard's verification matrix is `go test .\u002F...` at the repository root, never a curated package list. A guard that forbids a shape breaks every fixture that relied on it, including in packages the change never touched.\n- One worktree per writer, always, including the orchestrator. Before editing inline, check whether a delegated worker holds that path; if so, create a separate worktree rather than reusing it.\n- Audit every worker report yourself: re-run its key verification, decoy-test any new guard, spot-check its diffs. A self-report is a claim, not evidence.\n\n## Decision Gates\n\n| Condition | Action |\n| --- | --- |\n| Issue's failure mechanism absent from current main | Re-verify on latest build; close by rule A\u002FC or mark stale — never fix ghost code. |\n| Fix would add a mechanism, flag, or verb | Defer with written reason; re-rank for a deletion-shaped alternative first. |\n| Map contradicts the issue or your hypothesis | The map wins. Revise the plan and correct the public record (meta-issue) before coding. |\n| Blocker's fix lives in an unmerged PR | Leave open; it closes on merge or by its own thread condition. |\n| Closure evidence incomplete | Borderline list, not closure. |\n\n## Execution Steps\n\n1. Measure: read the cluster fully; partition by root; record counts in the meta-issue.\n2. Classify each issue against the real diff\u002Fcode; separate closes-via-X, improved-not-closed, unrelated, blocker.\n3. Map mechanisms read-only with anchors; flag mismatches.\n4. Rank fixes deletion-first; name D-items; get maintainer answers.\n5. Implement in slices (issue-first: every PR links a `status:approved` issue), audit each worker report.\n6. Hygiene pass: evidence-gated closures, stale-repro re-verification requests, meta-issue update with what changed and why.\n\n## Edge Cases\n\n- An issue filed before a fix merged is evidence about old builds, not a claim against current `main`.\n- When the mechanism map contradicts the hypothesis, the map wins and the plan must be revised first.\n- A fix that adds a new mechanism, flag, or verb is deferred until a deletion-shaped alternative is ruled out.\n\n## Output Contract\n\nPer pass, report: roots table (issues, fix shape, state), closures with rule+evidence, borderline list with reasons, D-items and their answers, mechanism-map mismatches found, and the meta-issue comment link.\n\n## References\n\n- `..\u002Frdd-advisory-transport\u002Freferences\u002Fshared-advisory-transport-proposal.md` — exemplar proposal shape produced by this method.\n- `..\u002Frdd-advisory-transport\u002Freferences\u002Fissue-impact-matrix.md` — exemplar per-issue disposition matrix.\n","## Activation Contract\n\nLoad when auditing a defect backlog for shared root causes, proposing a fix for an issue cluster, or closing issues as resolved\u002Foutdated. Complements `rdd-defect-workflow` (single-defect flow) — this skill governs the cluster-level method.\n\n## Hard Rules\n\n- Read full bodies and comments, never titles. Classify against the actual code or PR diff, not descriptions of it.\n- Verify every \"fixed\" or \"broken\" claim against current `origin\u002Fmain` the day you act. Compare report dates to fix merge dates: a repro filed before the fix landed is evidence about old builds, not current code.\n- Cluster defects by causal root, not surface. Each root gets a measured row in the meta-issue (#2471 style): issues attached, fix shape, state.\n- Before proposing any fix, produce a read-only mechanism map: one file:line anchor per claim, mechanism explained as implemented today. Report claim-vs-code mismatches explicitly; never force evidence to fit the hypothesis. Let the map shrink the proposal.\n- Rank solutions by what they DELETE: (1) removes a mechanism so the class becomes impossible, (2) static guard-ratchet making reintroduction a test failure, (3) localized predicate fix behind a failing repro test. New surface (verbs, flags, mechanisms) is last resort — defer until re-verified evidence demands it.\n- Extract maintainer choices as named D-items with recommended defaults. A maintainer condition recorded in an issue thread outranks any plan table, including yours.\n- Close only with evidence, one rule per closure: (A) fixed on main, cite commit AND proving test; (B) superseded by recorded maintainer decision; (C) surface no longer exists; (D) duplicate of a fixed issue. Comment before closing: what resolved it, verified today, reopen invitation. When in doubt, do not close — list as borderline.\n- Clean break, never compatibility. When a format or identity changes, bump its versioned tag as a REPLACEMENT: old records become outdated and fail closed with an actionable refusal naming the rerun. Never write dual recognition, legacy fallbacks, or compat shims; that residue is what the deletion criterion exists to prevent. Stored bytes are never rewritten and stay readable for forensics, but carry no gate or lifecycle validity.\n- Implementation follows the waves recipe: repro as failing test first, byte-stable goldens as defect signal, independently revertible slices, one writer per slice.\n- A universal guard's verification matrix is `go test .\u002F...` at the repository root, never a curated package list. A guard that forbids a shape breaks every fixture that relied on it, including in packages the change never touched.\n- One worktree per writer, always, including the orchestrator. Before editing inline, check whether a delegated worker holds that path; if so, create a separate worktree rather than reusing it.\n- Audit every worker report yourself: re-run its key verification, decoy-test any new guard, spot-check its diffs. A self-report is a claim, not evidence.\n\n## Decision Gates\n\n| Condition | Action |\n| --- | --- |\n| Issue's failure mechanism absent from current main | Re-verify on latest build; close by rule A\u002FC or mark stale — never fix ghost code. |\n| Fix would add a mechanism, flag, or verb | Defer with written reason; re-rank for a deletion-shaped alternative first. |\n| Map contradicts the issue or your hypothesis | The map wins. Revise the plan and correct the public record (meta-issue) before coding. |\n| Blocker's fix lives in an unmerged PR | Leave open; it closes on merge or by its own thread condition. |\n| Closure evidence incomplete | Borderline list, not closure. |\n\n## Execution Steps\n\n1. Measure: read the cluster fully; partition by root; record counts in the meta-issue.\n2. Classify each issue against the real diff\u002Fcode; separate closes-via-X, improved-not-closed, unrelated, blocker.\n3. Map mechanisms read-only with anchors; flag mismatches.\n4. Rank fixes deletion-first; name D-items; get maintainer answers.\n5. Implement in slices (issue-first: every PR links a `status:approved` issue), audit each worker report.\n6. Hygiene pass: evidence-gated closures, stale-repro re-verification requests, meta-issue update with what changed and why.\n\n## Edge Cases\n\n- An issue filed before a fix merged is evidence about old builds, not a claim against current `main`.\n- When the mechanism map contradicts the hypothesis, the map wins and the plan must be revised first.\n- A fix that adds a new mechanism, flag, or verb is deferred until a deletion-shaped alternative is ruled out.\n\n## Output Contract\n\nPer pass, report: roots table (issues, fix shape, state), closures with rule+evidence, borderline list with reasons, D-items and their answers, mechanism-map mismatches found, and the meta-issue comment link.\n\n## References\n\n- `..\u002Frdd-advisory-transport\u002Freferences\u002Fshared-advisory-transport-proposal.md` — exemplar proposal shape produced by this method.\n- `..\u002Frdd-advisory-transport\u002Freferences\u002Fissue-impact-matrix.md` — exemplar per-issue disposition matrix.\n",{"name":5,"license":14,"metadata":42,"triggers":45,"description":7},{"author":43,"version":44},"gentleman-programming","1.0","root audit, issue roots, backlog roots, mechanism map, deletion-driven fix, close outdated issues, root cause","main","4af6946b30783e2c8f9182082324d530fc28f838",".agents\u002Fskills\u002Fissue-root-resolution","https:\u002F\u002Fgithub.com\u002FLuisAlbertoMK\u002Fgentleman-agent-gh","https:\u002F\u002Fgithub.com\u002FLuisAlbertoMK","2026-11-10 18:34:27",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add LuisAlbertoMK\u002Fgentleman-agent-gh --skill issue-root-resolution",{"tool":58,"command":59},"bunx","bunx skills add LuisAlbertoMK\u002Fgentleman-agent-gh --skill issue-root-resolution",{"tool":61,"command":62},"pnpm","pnpm dlx skills add LuisAlbertoMK\u002Fgentleman-agent-gh --skill issue-root-resolution","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLuisAlbertoMK\u002Fgentleman-agent-gh\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fissue-root-resolution\u002FSKILL.md",true,[],[67,109,132,151,176,202],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":89,"publishedAt":37},"01M71R7K35P668DYEPYGDQP2QA","web-quality-audit","Comprehensive web audit: performance, a11y, SEO, responsive, animation, design tokens.","https:\u002F\u002Fgithub.com\u002FLuisAlbertoMK\u002Fgentleman-agent-gh\u002Fblob\u002Fmain\u002Fdocs\u002Fciclos\u002Fc28-w1-backup\u002Fweb-quality-audit\u002FSKILL.md",[73,78,81,86],{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":79,"categoryName":80,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":87,"categoryName":88,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000035","市场营销",[90,91,92,36,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108],"quality","quality audit","web quality audit","web","Animation","design audit","design","website","ui","responsive","seo","tokens","ui audit","Lighthouse","performance","review","optimize","a11y","page",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":116,"publishedAt":37},"01M71R7H1RA7CQ568DHRK37PE2","ui-engine","UI system — Grid\u002FFlexbox\u002F@layer\u002F:has(), container queries, compositor-only animation, OKLCH tokens, component patterns","https:\u002F\u002Fgithub.com\u002FLuisAlbertoMK\u002Fgentleman-agent-gh\u002Fblob\u002Fmain\u002Fdocs\u002Fciclos\u002Fc28-w1-backup\u002Fui-engine\u002FSKILL.md",[115],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[117,118,98,94,119,120,121,108,122,101,123,124,125,96,126,127,128,129,130,131],"ui engine","engine","compositor","css","dark","system","mode","hooks","container","only","query","components","dark mode","grid","queries",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":140,"publishedAt":37},"01M71R7EPMZFKB833WE4B3GTHC","baseline-ui","Anti-slop UI — layout, typography, responsive, animation, tokens. Use for cleanup or polish.","https:\u002F\u002Fgithub.com\u002FLuisAlbertoMK\u002Fgentleman-agent-gh\u002Fblob\u002Fmain\u002Fdocs\u002Fciclos\u002Fc28-w1-backup\u002Fbaseline-ui\u002FSKILL.md",[138,139],{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[141,142,98,94,143,144,145,146,101,34,125,96,147,148,149,102,150,127,130,105],"baseline ui","baseline","generic","slop","for","anti-slop","interface","cleanup","design review","use",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":160,"publishedAt":37},"01M71R7CWK3FBW77Z8WD9GXQFE","skill-creator","Create new AI agent skills following Agent Skills spec -- auto-bootstrap unknown tasks, define structure, register in AGENTS.md","https:\u002F\u002Fgithub.com\u002FLuisAlbertoMK\u002Fgentleman-agent-gh\u002Fblob\u002Fmain\u002F.archive\u002Fskills\u002Fskill-creator\u002FSKILL.md",[157],{"categoryNo":158,"categoryName":159,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000023","Skill与智能体开发",[161,162,163,164,165,166,167,168,169,170,171,172,173,174,175],"skill creator","creator","create","structure","register","2026","spec","new","ai skill","auto","define","ai agent","unknown","tasks","bootstrap",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":184,"publishedAt":37},"01M71R78DZM1GA16F1KN8ND926","senior-engineer","Apply senior engineering competencies — system design, trade-off analysis, delegation, mentoring, and tech debt strategy","https:\u002F\u002Fgithub.com\u002FLuisAlbertoMK\u002Fgentleman-agent-gh\u002Fblob\u002Fmain\u002F.archive\u002Fskills\u002Fsenior-engineer\u002FSKILL.md",[182,183],{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[185,186,187,188,189,190,191,96,192,193,166,194,195,196,122,197,198,199,200,201],"engineer","senior","senior engineer","system design","trade-offs","senior engineering","delegation","senior architect","analysis","debt","architect","tech","strategy","apply","trade","tech debt","engineering",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":212,"publishedAt":37},"01M71R74WQTXZMG3219RND96CE","prompt-engineering","Design effective prompts using SPEARS framework — scope, principles, examples, assertions, refinements, with ReAct and multi-agent patterns","https:\u002F\u002Fgithub.com\u002FLuisAlbertoMK\u002Fgentleman-agent-gh\u002Fblob\u002Fmain\u002F.archive\u002Fskills\u002Fprompt-engineering\u002FSKILL.md",[208,211],{"categoryNo":209,"categoryName":210,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":158,"categoryName":159,"taxonomyType":76,"taxonomyTypeDesc":77},[213,214,201,215,216,96,217,166,218,219,220,221,222,223,224,225,226,227,228,229],"prompt","prompt engineering","scope","improve","react","security","patterns","multi-agent","framework","agent patterns","assertions","examples","with","multi","principles","improve prompt","prompts"]