[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FEVA6RJMEWJA3X3WV5NAPR":3,"skill-same:01M7FEVA6RJMEWJA3X3WV5NAPR":46},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7FEVA6RJMEWJA3X3WV5NAPR","gitnexus-pdg-query",null,"Use when querying or extending GitNexus's PDG control\u002Fdata-dependence surface (the `pdg_query` MCP tool, CDG\u002FREACHING_DEF edges), or reasoning about \"what controls X\" \u002F \"where does Y flow\" \u002F guard clauses. Examples: \"what guards this statement?\", \"trace this variable within the function\", \"why is the pdg_query result empty?\", \"add a CDG query\".","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fgitnexus-pdg-query\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: gitnexus-pdg-query\ndescription: \"Use when querying or extending GitNexus's PDG control\u002Fdata-dependence surface (the `pdg_query` MCP tool, CDG\u002FREACHING_DEF edges), or reasoning about \\\"what controls X\\\" \u002F \\\"where does Y flow\\\" \u002F guard clauses. Examples: \\\"what guards this statement?\\\", \\\"trace this variable within the function\\\", \\\"why is the pdg_query result empty?\\\", \\\"add a CDG query\\\".\"\n---\n\n# PDG query surface with GitNexus\n\nExpert knowledge for the `pdg_query` MCP tool and the control\u002Fdata-dependence\nedges it reads — the opt-in `--pdg` program-dependence layers. Read this before\ntouching `gitnexus\u002Fsrc\u002Fmcp\u002Flocal\u002Flocal-backend.ts` (`_pdgQueryImpl`) or the\n`pdg_query` tool def, or when explaining a `pdg_query` result.\n\n## When to Use\n\n- \"Under what condition does this statement run?\" (guarding predicates).\n- \"Where does this variable flow inside the function?\" (def→use).\n- Guard-clause discovery (early-return guards — subsumes the #559 heuristic).\n- Extending or reviewing `pdg_query` \u002F the CDG \u002F REACHING_DEF read path.\n- Debugging an empty or surprising `pdg_query` result.\n\n## The layered substrate (build order)\n\n`pdg_query` runs **on** the same graph taint runs on. Each layer is opt-in\nbehind `--pdg`; a default `analyze` run records none of them (byte-identical).\n\n```\nL1  CFG            per-function basic blocks + control-flow edges   (M1 #2081)\nL2  REACHING_DEF   GEN\u002FKILL def→use data dependence (pure solver)   (M2 #2082)\nL5  CDG            Ferrante control dependence (post-dominators)    (M5 #2085)\n```\n\nAll three are `BasicBlock → BasicBlock` edges in the single `CodeRelation` table\n(keyed by the `type` property). There is **no** `Function → BasicBlock` edge.\n\n## The two modes\n\n- `pdg_query({ mode: 'controls', target })` — CDG. For the anchored function,\n  each edge: controlling predicate block → dependent block + branch sense in\n  `label` (`'T'` = predicate's true\u002Ftaken arm, `'F'` = false\u002Ffall-through). An\n  edge into an early-return\u002Fthrow block is flagged `guard: true`.\n- `pdg_query({ mode: 'flows', target, variable? })` — REACHING_DEF def→use\n  edges; `variable` filters to one binding.\n\n`target` is **required** — a file path or a symbol\u002Ffunction name (resolved like\n`context()`). There is no anchorless mode (see below).\n\n## The corrected guard-clause Cypher\n\nThe RFC #567 §2 form (`[:CDG {label:'F'}]`) does **not** run as written. Edges\nare values of the single `CodeRelation` table's `type` property, and the branch\nsense is in `reason`, NOT a `label` column:\n\n```cypher\nMATCH (pred:BasicBlock)-[r:CodeRelation {type: 'CDG'}]->(dep:BasicBlock)\nWHERE dep.text STARTS WITH 'return' OR dep.text STARTS WITH 'throw'\nRETURN pred.startLine, r.reason AS branch, dep.startLine, dep.text\n```\n\n`r.reason` is the sense the predicate took to reach the early exit. For\n`if (!ok) return;` the return rides the predicate's **true** arm (`'T'`) and the\nprotected body rides the **false** arm (`'F'`) — polarity depends on the guard,\nso don't hard-code one sense.\n\n## Gotchas (the load-bearing ones)\n\n- **Always anchored + LIMIT-bounded.** LadybugDB has no rel-property index, so\n  an unanchored `[:CDG*]`\u002F`[:REACHING_DEF*]` path scan is unbounded. `pdg_query`\n  requires `target` and bounds the page; raw `cypher` callers must anchor on a\n  file id-prefix or symbol span themselves.\n- **BasicBlock↔symbol join is reconstructed.** No `Function→BasicBlock` edge:\n  the block is matched by its id-prefix (`BasicBlock:\u003Cfile>:\u003CfnStartLine>:…`)\n  plus `startLine` within the symbol's span. BasicBlock `startLine` is **1-based**\n  while the symbol node's `startLine`\u002F`endLine` are **0-based**, so **both** bounds\n  are shifted `+1` (`[symStart+1, symEnd+1]`): the upper `+1` keeps a guard\u002Fdef\u002Fuse\n  on the function's **final line**, the lower `+1` excludes an adjacent function's\n  block on the line directly **above**. Same-line \u002F nested functions anchor coarsely.\n- **No PDG layer ⇒ a note, not an error.** If the repo wasn't indexed with\n  `--pdg` the tool returns `{ results: [], note: \"no PDG layer …\" }` (cheap meta\n  probe on `RepoMeta.pdg.maxCdgEdgesPerFunction` \u002F `maxReachingDefEdgesPerFunction`).\n- **CDG labels are binary in M5\u002FM6.** Every `switch`-case arm is `'T'`; per-case\n  conditions are not yet distinguished.\n- **Intra-procedural only.** Cross-function flow is taint's domain (`explain`).\n\n## Mirror, don't fork\n\n`_pdgQueryImpl` is the front half of `_explainImpl` (WAL wrapper, meta no-layer\nprobe, limit validation, `resolveSymbolCandidates` anchoring) with CDG\u002F\nREACHING_DEF instead of TAINTED — and none of taint's path-codec \u002F interproc\n`TAINT_PATH` machinery. Reuse those shared helpers; do not re-implement them.\n","# PDG query surface with GitNexus\n\nExpert knowledge for the `pdg_query` MCP tool and the control\u002Fdata-dependence\nedges it reads — the opt-in `--pdg` program-dependence layers. Read this before\ntouching `gitnexus\u002Fsrc\u002Fmcp\u002Flocal\u002Flocal-backend.ts` (`_pdgQueryImpl`) or the\n`pdg_query` tool def, or when explaining a `pdg_query` result.\n\n## When to Use\n\n- \"Under what condition does this statement run?\" (guarding predicates).\n- \"Where does this variable flow inside the function?\" (def→use).\n- Guard-clause discovery (early-return guards — subsumes the #559 heuristic).\n- Extending or reviewing `pdg_query` \u002F the CDG \u002F REACHING_DEF read path.\n- Debugging an empty or surprising `pdg_query` result.\n\n## The layered substrate (build order)\n\n`pdg_query` runs **on** the same graph taint runs on. Each layer is opt-in\nbehind `--pdg`; a default `analyze` run records none of them (byte-identical).\n\n```\nL1  CFG            per-function basic blocks + control-flow edges   (M1 #2081)\nL2  REACHING_DEF   GEN\u002FKILL def→use data dependence (pure solver)   (M2 #2082)\nL5  CDG            Ferrante control dependence (post-dominators)    (M5 #2085)\n```\n\nAll three are `BasicBlock → BasicBlock` edges in the single `CodeRelation` table\n(keyed by the `type` property). There is **no** `Function → BasicBlock` edge.\n\n## The two modes\n\n- `pdg_query({ mode: 'controls', target })` — CDG. For the anchored function,\n  each edge: controlling predicate block → dependent block + branch sense in\n  `label` (`'T'` = predicate's true\u002Ftaken arm, `'F'` = false\u002Ffall-through). An\n  edge into an early-return\u002Fthrow block is flagged `guard: true`.\n- `pdg_query({ mode: 'flows', target, variable? })` — REACHING_DEF def→use\n  edges; `variable` filters to one binding.\n\n`target` is **required** — a file path or a symbol\u002Ffunction name (resolved like\n`context()`). There is no anchorless mode (see below).\n\n## The corrected guard-clause Cypher\n\nThe RFC #567 §2 form (`[:CDG {label:'F'}]`) does **not** run as written. Edges\nare values of the single `CodeRelation` table's `type` property, and the branch\nsense is in `reason`, NOT a `label` column:\n\n```cypher\nMATCH (pred:BasicBlock)-[r:CodeRelation {type: 'CDG'}]->(dep:BasicBlock)\nWHERE dep.text STARTS WITH 'return' OR dep.text STARTS WITH 'throw'\nRETURN pred.startLine, r.reason AS branch, dep.startLine, dep.text\n```\n\n`r.reason` is the sense the predicate took to reach the early exit. For\n`if (!ok) return;` the return rides the predicate's **true** arm (`'T'`) and the\nprotected body rides the **false** arm (`'F'`) — polarity depends on the guard,\nso don't hard-code one sense.\n\n## Gotchas (the load-bearing ones)\n\n- **Always anchored + LIMIT-bounded.** LadybugDB has no rel-property index, so\n  an unanchored `[:CDG*]`\u002F`[:REACHING_DEF*]` path scan is unbounded. `pdg_query`\n  requires `target` and bounds the page; raw `cypher` callers must anchor on a\n  file id-prefix or symbol span themselves.\n- **BasicBlock↔symbol join is reconstructed.** No `Function→BasicBlock` edge:\n  the block is matched by its id-prefix (`BasicBlock:\u003Cfile>:\u003CfnStartLine>:…`)\n  plus `startLine` within the symbol's span. BasicBlock `startLine` is **1-based**\n  while the symbol node's `startLine`\u002F`endLine` are **0-based**, so **both** bounds\n  are shifted `+1` (`[symStart+1, symEnd+1]`): the upper `+1` keeps a guard\u002Fdef\u002Fuse\n  on the function's **final line**, the lower `+1` excludes an adjacent function's\n  block on the line directly **above**. Same-line \u002F nested functions anchor coarsely.\n- **No PDG layer ⇒ a note, not an error.** If the repo wasn't indexed with\n  `--pdg` the tool returns `{ results: [], note: \"no PDG layer …\" }` (cheap meta\n  probe on `RepoMeta.pdg.maxCdgEdgesPerFunction` \u002F `maxReachingDefEdgesPerFunction`).\n- **CDG labels are binary in M5\u002FM6.** Every `switch`-case arm is `'T'`; per-case\n  conditions are not yet distinguished.\n- **Intra-procedural only.** Cross-function flow is taint's domain (`explain`).\n\n## Mirror, don't fork\n\n`_pdgQueryImpl` is the front half of `_explainImpl` (WAL wrapper, meta no-layer\nprobe, limit validation, `resolveSymbolCandidates` anchoring) with CDG\u002F\nREACHING_DEF instead of TAINTED — and none of taint's path-codec \u002F interproc\n`TAINT_PATH` machinery. Reuse those shared helpers; do not re-implement them.\n",{"name":5,"description":7},"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","07-后端与架构\u002Fgitnexus-pdg-query",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill gitnexus-pdg-query",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill gitnexus-pdg-query",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill gitnexus-pdg-query","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fgitnexus-pdg-query\u002FSKILL.md",true,[],[47,54,59,66,73,80],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":55,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]