[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FETR2WZ83K5JS1Z1J3BVV5":3,"skill-same:01M7FETR2WZ83K5JS1Z1J3BVV5":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},"01M7FETR2WZ83K5JS1Z1J3BVV5","gitnexus-debugging",null,"Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: \"Why is X failing?\", \"Where does this error come from?\", \"Trace this bug\"","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-debugging\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: gitnexus-debugging\ndescription: \"Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: \\\"Why is X failing?\\\", \\\"Where does this error come from?\\\", \\\"Trace this bug\\\"\"\n---\n\n# Debugging with GitNexus\n\n## When to Use\n\n- \"Why is this function failing?\"\n- \"Trace where this error comes from\"\n- \"Who calls this method?\"\n- \"This endpoint returns 500\"\n- Investigating bugs, errors, or unexpected behavior\n\n## Bind the repository first\n\nA root cause traced in the wrong repository is a wrong root cause.\n\nCall `list_repos {}` before the first tool call. With one indexed repository,\nuse the examples below as written. With more than one, pass `repo` on every\ncall: an omitted `repo` normally errors, but under an MCP policy with a\nconfigured default it resolves to that default silently. If you cannot tell\nwhich repository is meant, stop and ask. This matters most for `cypher`, whose\nstatement carries no in-band hint of which database it ran against.\n\n`list_repos` is paginated, so page with `offset: pagination.nextOffset` until\n`hasMore` is false before concluding a repository is absent.\n\nA stale index describes the code from before your bug, so refresh before\ntrusting a trace, and state the repository and index freshness with the\ndiagnosis.\n\n## Workflow\n\n```\n0. list_repos {}                                          → Bind repo\n1. query({search_query: \"\u003Cerror or symptom>\"})            → Find related execution flows\n2. context({name: \"\u003Csuspect>\"})                    → See callers\u002Fcallees\u002Fprocesses\n3. READ gitnexus:\u002F\u002Frepo\u002F{name}\u002Fprocess\u002F{name}                → Trace execution flow\n4. cypher({statement: \"MATCH path...\"})                 → Custom traces if needed\n```\n\n> If \"Index is stale\" → run `node .gitnexus\u002Frun.cjs analyze` in terminal.\n\n## Checklist\n\n```\n- [ ] list_repos {} — bind repo; explicit repo when >1 indexed, ask if ambiguous\n- [ ] Understand the symptom (error message, unexpected behavior)\n- [ ] query for error text or related code\n- [ ] Identify the suspect function from returned processes\n- [ ] context to see callers and callees\n- [ ] Trace execution flow via process resource if applicable\n- [ ] cypher for custom call chain traces if needed\n- [ ] Read source files to confirm root cause\n- [ ] State the repository and index freshness with the diagnosis\n```\n\n## Debugging Patterns\n\n| Symptom              | GitNexus Approach                                          |\n| -------------------- | ---------------------------------------------------------- |\n| Error message        | `query` for error text → `context` on throw sites |\n| Wrong return value   | `context` on the function → trace callees for data flow    |\n| Intermittent failure | `context` → look for external calls, async deps            |\n| Performance issue    | `context` → find symbols with many callers (hot paths)     |\n| Recent regression    | `detect_changes` to see what your changes affect — pass `worktree` for a linked worktree |\n| \"How does A reach B?\" | `trace` between the two symbols — shortest call chain in one call |\n\n## Tools\n\n**query** — find code related to error:\n\n```\nquery({search_query: \"payment validation error\", repo: \"my-app\"})\n→ Processes: CheckoutFlow, ErrorHandling\n→ Symbols: validatePayment, handlePaymentError, PaymentException\n```\n\n**context** — full context for a suspect:\n\n```\ncontext({name: \"validatePayment\", repo: \"my-app\"})\n→ Incoming calls: processCheckout, webhookHandler\n→ Outgoing calls: verifyCard, fetchRates (external API!)\n→ Processes: CheckoutFlow (step 3\u002F7)\n```\n\n**cypher** — custom call chain traces. Pass `repo` alongside the statement; the\nCypher text itself names no repository, so the result is unattributable without\nit:\n\n```cypher\nMATCH path = (a)-[:CodeRelation {type: 'CALLS'}*1..2]->(b:Function {name: \"validatePayment\"})\nRETURN [n IN nodes(path) | n.name] AS chain\n```\n\n**trace** — shortest call chain between two symbols (\"how does A reach B?\"), one call instead of chaining `context` hops:\n\n```\ntrace({ from: \"processCheckout\", to: \"fetchRates\", repo: \"my-app\" })\n→ status: ok, hopCount: 3\n→ hops: processCheckout → validatePayment → verifyCard → fetchRates\n→ edges: CALLS (1.0), CALLS (0.95), CALLS (1.0)\n```\n\nWhen no path exists, `trace` reports the furthest reachable node — exactly where the chain breaks (dynamic dispatch, reflection, or an external boundary).\n\n## Example: \"Payment endpoint returns 500 intermittently\"\n\n```\n0. list_repos {}\n   → total: 2 (my-app, billing-api) — bind my-app explicitly on every call\n\n1. query({search_query: \"payment error handling\", repo: \"my-app\"})\n   → Processes: CheckoutFlow, ErrorHandling\n   → Symbols: validatePayment, handlePaymentError\n\n2. context({name: \"validatePayment\", repo: \"my-app\"})\n   → Outgoing calls: verifyCard, fetchRates (external API!)\n\n3. READ gitnexus:\u002F\u002Frepo\u002Fmy-app\u002Fprocess\u002FCheckoutFlow\n   → Step 3: validatePayment → calls fetchRates (external)\n\n4. Root cause: fetchRates calls external API without proper timeout\n   Repository: my-app  Index: current\n```\n\nWith a single indexed repository, step 0 returns `total: 1` and the `repo`\nargument drops out of every call above.\n","# Debugging with GitNexus\n\n## When to Use\n\n- \"Why is this function failing?\"\n- \"Trace where this error comes from\"\n- \"Who calls this method?\"\n- \"This endpoint returns 500\"\n- Investigating bugs, errors, or unexpected behavior\n\n## Bind the repository first\n\nA root cause traced in the wrong repository is a wrong root cause.\n\nCall `list_repos {}` before the first tool call. With one indexed repository,\nuse the examples below as written. With more than one, pass `repo` on every\ncall: an omitted `repo` normally errors, but under an MCP policy with a\nconfigured default it resolves to that default silently. If you cannot tell\nwhich repository is meant, stop and ask. This matters most for `cypher`, whose\nstatement carries no in-band hint of which database it ran against.\n\n`list_repos` is paginated, so page with `offset: pagination.nextOffset` until\n`hasMore` is false before concluding a repository is absent.\n\nA stale index describes the code from before your bug, so refresh before\ntrusting a trace, and state the repository and index freshness with the\ndiagnosis.\n\n## Workflow\n\n```\n0. list_repos {}                                          → Bind repo\n1. query({search_query: \"\u003Cerror or symptom>\"})            → Find related execution flows\n2. context({name: \"\u003Csuspect>\"})                    → See callers\u002Fcallees\u002Fprocesses\n3. READ gitnexus:\u002F\u002Frepo\u002F{name}\u002Fprocess\u002F{name}                → Trace execution flow\n4. cypher({statement: \"MATCH path...\"})                 → Custom traces if needed\n```\n\n> If \"Index is stale\" → run `node .gitnexus\u002Frun.cjs analyze` in terminal.\n\n## Checklist\n\n```\n- [ ] list_repos {} — bind repo; explicit repo when >1 indexed, ask if ambiguous\n- [ ] Understand the symptom (error message, unexpected behavior)\n- [ ] query for error text or related code\n- [ ] Identify the suspect function from returned processes\n- [ ] context to see callers and callees\n- [ ] Trace execution flow via process resource if applicable\n- [ ] cypher for custom call chain traces if needed\n- [ ] Read source files to confirm root cause\n- [ ] State the repository and index freshness with the diagnosis\n```\n\n## Debugging Patterns\n\n| Symptom              | GitNexus Approach                                          |\n| -------------------- | ---------------------------------------------------------- |\n| Error message        | `query` for error text → `context` on throw sites |\n| Wrong return value   | `context` on the function → trace callees for data flow    |\n| Intermittent failure | `context` → look for external calls, async deps            |\n| Performance issue    | `context` → find symbols with many callers (hot paths)     |\n| Recent regression    | `detect_changes` to see what your changes affect — pass `worktree` for a linked worktree |\n| \"How does A reach B?\" | `trace` between the two symbols — shortest call chain in one call |\n\n## Tools\n\n**query** — find code related to error:\n\n```\nquery({search_query: \"payment validation error\", repo: \"my-app\"})\n→ Processes: CheckoutFlow, ErrorHandling\n→ Symbols: validatePayment, handlePaymentError, PaymentException\n```\n\n**context** — full context for a suspect:\n\n```\ncontext({name: \"validatePayment\", repo: \"my-app\"})\n→ Incoming calls: processCheckout, webhookHandler\n→ Outgoing calls: verifyCard, fetchRates (external API!)\n→ Processes: CheckoutFlow (step 3\u002F7)\n```\n\n**cypher** — custom call chain traces. Pass `repo` alongside the statement; the\nCypher text itself names no repository, so the result is unattributable without\nit:\n\n```cypher\nMATCH path = (a)-[:CodeRelation {type: 'CALLS'}*1..2]->(b:Function {name: \"validatePayment\"})\nRETURN [n IN nodes(path) | n.name] AS chain\n```\n\n**trace** — shortest call chain between two symbols (\"how does A reach B?\"), one call instead of chaining `context` hops:\n\n```\ntrace({ from: \"processCheckout\", to: \"fetchRates\", repo: \"my-app\" })\n→ status: ok, hopCount: 3\n→ hops: processCheckout → validatePayment → verifyCard → fetchRates\n→ edges: CALLS (1.0), CALLS (0.95), CALLS (1.0)\n```\n\nWhen no path exists, `trace` reports the furthest reachable node — exactly where the chain breaks (dynamic dispatch, reflection, or an external boundary).\n\n## Example: \"Payment endpoint returns 500 intermittently\"\n\n```\n0. list_repos {}\n   → total: 2 (my-app, billing-api) — bind my-app explicitly on every call\n\n1. query({search_query: \"payment error handling\", repo: \"my-app\"})\n   → Processes: CheckoutFlow, ErrorHandling\n   → Symbols: validatePayment, handlePaymentError\n\n2. context({name: \"validatePayment\", repo: \"my-app\"})\n   → Outgoing calls: verifyCard, fetchRates (external API!)\n\n3. READ gitnexus:\u002F\u002Frepo\u002Fmy-app\u002Fprocess\u002FCheckoutFlow\n   → Step 3: validatePayment → calls fetchRates (external)\n\n4. Root cause: fetchRates calls external API without proper timeout\n   Repository: my-app  Index: current\n```\n\nWith a single indexed repository, step 0 returns `total: 1` and the `repo`\nargument drops out of every call above.\n",{"name":5,"description":7},"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","07-后端与架构\u002Fgitnexus-debugging",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-debugging",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill gitnexus-debugging",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill gitnexus-debugging","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fgitnexus-debugging\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",[],[]]