[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DBMN3DYK7W0Z2TVG04DRYW":3,"skill-same:01M7DBMN3DYK7W0Z2TVG04DRYW":99},{"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":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7DBMN3DYK7W0Z2TVG04DRYW","architecture-governance",null,"Check ZCode module and layer boundaries for code changes. Generate bounded context for cross-module or ownership changes; skip documentation-only work.","ZCodium-project\u002FZCodium","ZCodium-project","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F331969751?v=4","01M7DBKVDM2CY9G27NC8F39MCG","ZCodium","01M7DBKVEPNTJN0R8FNRV88JEH",253,"MIT","https:\u002F\u002Fgithub.com\u002FZCodium-project\u002FZCodium\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Farchitecture-governance\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: architecture-governance\ndescription: Check ZCode module and layer boundaries for code changes. Generate bounded context for cross-module or ownership changes; skip documentation-only work.\n---\n\n# Architecture governance\n\nUse this skill before editing code in the ZCode repository. It is a design guide as well as a gate: the goal is to make the intended architecture obvious before code is generated, so the checker confirms a decision instead of discovering it for the first time.\n\n## Before writing code\n\n1. Identify intended files and modules from the task, contracts, and existing tests. Run `pnpm architecture:check --changed` for the current baseline; a clean diff does not identify files you have not edited yet.\n2. For cross-module changes, state ownership changes, or an unclear contract, run `pnpm architecture:context \u003Cmodule-id>` (or `node .agents\u002Fskills\u002Farchitecture-governance\u002Fscripts\u002Fcontext-package.mjs \u003Cmodule-id>`). For a local change with a known contract, read only the relevant contract, spec, and affected tests; expand when a concrete dependency or evidence gap requires it.\n3. Apply the spec and regression-evidence rules in [AGENTS.md](..\u002F..\u002F..\u002FAGENTS.md). New behavior needs a spec before implementation; restoring already specified behavior needs regression evidence, not a duplicate feature document. Pure refactors update docs only when contracts change.\n4. For changes to mutable state, asynchronous behavior, or module boundaries, make the relevant design decisions before coding:\n   - **One owner:** name the single component that owns each piece of mutable state. Other layers read through its contract and send commands; they do not keep a second accepted queue, cache, or derived truth.\n   - **One path:** reuse an existing command, service, hook, adapter, or contract when it already expresses the behavior. Do not create a parallel helper for the same responsibility.\n   - **Explicit boundaries:** choose the layer for every new file and the public contract for every cross-module edge. Layers from low to high are `contract \u003C domain \u003C app \u003C adapters \u003C ui`; a file may import only its own layer or lower ones through their public surface. `domain` is pure (no IO, no `await` on the world), `app` decides side effects through ports, `adapters` executes them, `ui` depends only on this module's `contract.ts`. Quick test: needs `await`? not domain. Knows it is sqlite \u002F MessagePort \u002F a timer? adapters.\n   - **Explicit time:** for asynchronous or remote behavior, write the event order, owner\u002Flease, idempotency key, stale-result rule, replay\u002Fresume boundary, and desktop versus mobile delivery kind before implementation.\n   - **Bounded context:** use the relevant contracts, specs, and tests. A generated reading package helps when dependencies are unclear; do not require a whole-module reading pass for every local edit.\n5. If the change alters a public contract, ownership, or allowed dependency, record that decision in the relevant spec\u002Fcontract before implementation. Editing files in two modules alone does not require a new document. Use the root task boundary for when to consult the user; ordinary authorized implementation choices proceed autonomously.\n\nUse this compact design sketch while planning stateful changes:\n\n```text\ninput → single owner → command admission → state transition → contract\u002Fevent\n                  └── persistence \u002F replay \u002F projection are derived from the owner\n```\n\nFor remote or streaming changes, make the delivery boundary explicit:\n\n```text\ndesktop: continuous ── direct live stream ──┐\n                                           ├─ same owner and sequence\nmobile: replayable ─ snapshot + gap repair ┘\n```\n\n## During and after editing\n\n6. Keep changes inside the declared module and its allowed layer direction. Add a module dependency or public contract before introducing a cross-module edge.\n7. Run `pnpm architecture:check --changed` after editing. Report new violations separately from baseline violations; include owners and event-order assumptions when affected. Follow the root validation matrix, finish after required checks pass, and expand checks only for new edits, failures, or unresolved risks.\n\nThe executable policy is `architecture-policy.yaml`; keep its detailed rule definitions there. Check the actual managed-module coverage before claiming the gate verifies a boundary: a passing result does not prove unconfigured modules or runtime semantics are correct. Use `pnpm architecture:baseline:update` only when a reviewed change intentionally changes the accepted legacy baseline. CI never refreshes baseline automatically.\n\nEvery new source file under `packages\u002F` or `apps\u002F` must belong to a managed module (rule `unmanaged-new-file`). When the change needs a directory that is not managed yet, register it first:\n\n```text\npnpm architecture:adopt \u003Cmodule-id> --root \u003Cdir> [--root \u003Cdir2>] --layer \u003Cdomain|app|adapters|ui> [--owner \u003Cgroup>]\n```\n\n`adopt` infers `requires` from the real imports, scaffolds the five artifacts if missing, and registers the module in `architecture-policy.yaml` without touching existing comments. Fill `contract.ts` and `CONTRACT.md` before adding behavior; keep the module's public surface to one intent per method.\n\nFor a new managed module, provide `module.ts`, `contract.ts`, `contract.example.ts`, `contract.test.ts`, and a short `CONTRACT.md`. Keep runtime and persistence details behind the contract. Prefer typed service calls for one-to-one interactions, commands for state changes, and typed events for broadcast facts.\n\nSee [policy-schema.md](references\u002Fpolicy-schema.md), [module-contract.md](references\u002Fmodule-contract.md), and [rule-catalog.md](references\u002Frule-catalog.md) when the change needs their detailed guidance. The [golden-module](references\u002Fgolden-module) fixture is the smallest compliant example.\nSee [ai-guidance.md](references\u002Fai-guidance.md) for the anti-patterns this workflow is designed to prevent and the questions an agent must answer before proposing code.\n","# Architecture governance\n\nUse this skill before editing code in the ZCode repository. It is a design guide as well as a gate: the goal is to make the intended architecture obvious before code is generated, so the checker confirms a decision instead of discovering it for the first time.\n\n## Before writing code\n\n1. Identify intended files and modules from the task, contracts, and existing tests. Run `pnpm architecture:check --changed` for the current baseline; a clean diff does not identify files you have not edited yet.\n2. For cross-module changes, state ownership changes, or an unclear contract, run `pnpm architecture:context \u003Cmodule-id>` (or `node .agents\u002Fskills\u002Farchitecture-governance\u002Fscripts\u002Fcontext-package.mjs \u003Cmodule-id>`). For a local change with a known contract, read only the relevant contract, spec, and affected tests; expand when a concrete dependency or evidence gap requires it.\n3. Apply the spec and regression-evidence rules in [AGENTS.md](..\u002F..\u002F..\u002FAGENTS.md). New behavior needs a spec before implementation; restoring already specified behavior needs regression evidence, not a duplicate feature document. Pure refactors update docs only when contracts change.\n4. For changes to mutable state, asynchronous behavior, or module boundaries, make the relevant design decisions before coding:\n   - **One owner:** name the single component that owns each piece of mutable state. Other layers read through its contract and send commands; they do not keep a second accepted queue, cache, or derived truth.\n   - **One path:** reuse an existing command, service, hook, adapter, or contract when it already expresses the behavior. Do not create a parallel helper for the same responsibility.\n   - **Explicit boundaries:** choose the layer for every new file and the public contract for every cross-module edge. Layers from low to high are `contract \u003C domain \u003C app \u003C adapters \u003C ui`; a file may import only its own layer or lower ones through their public surface. `domain` is pure (no IO, no `await` on the world), `app` decides side effects through ports, `adapters` executes them, `ui` depends only on this module's `contract.ts`. Quick test: needs `await`? not domain. Knows it is sqlite \u002F MessagePort \u002F a timer? adapters.\n   - **Explicit time:** for asynchronous or remote behavior, write the event order, owner\u002Flease, idempotency key, stale-result rule, replay\u002Fresume boundary, and desktop versus mobile delivery kind before implementation.\n   - **Bounded context:** use the relevant contracts, specs, and tests. A generated reading package helps when dependencies are unclear; do not require a whole-module reading pass for every local edit.\n5. If the change alters a public contract, ownership, or allowed dependency, record that decision in the relevant spec\u002Fcontract before implementation. Editing files in two modules alone does not require a new document. Use the root task boundary for when to consult the user; ordinary authorized implementation choices proceed autonomously.\n\nUse this compact design sketch while planning stateful changes:\n\n```text\ninput → single owner → command admission → state transition → contract\u002Fevent\n                  └── persistence \u002F replay \u002F projection are derived from the owner\n```\n\nFor remote or streaming changes, make the delivery boundary explicit:\n\n```text\ndesktop: continuous ── direct live stream ──┐\n                                           ├─ same owner and sequence\nmobile: replayable ─ snapshot + gap repair ┘\n```\n\n## During and after editing\n\n6. Keep changes inside the declared module and its allowed layer direction. Add a module dependency or public contract before introducing a cross-module edge.\n7. Run `pnpm architecture:check --changed` after editing. Report new violations separately from baseline violations; include owners and event-order assumptions when affected. Follow the root validation matrix, finish after required checks pass, and expand checks only for new edits, failures, or unresolved risks.\n\nThe executable policy is `architecture-policy.yaml`; keep its detailed rule definitions there. Check the actual managed-module coverage before claiming the gate verifies a boundary: a passing result does not prove unconfigured modules or runtime semantics are correct. Use `pnpm architecture:baseline:update` only when a reviewed change intentionally changes the accepted legacy baseline. CI never refreshes baseline automatically.\n\nEvery new source file under `packages\u002F` or `apps\u002F` must belong to a managed module (rule `unmanaged-new-file`). When the change needs a directory that is not managed yet, register it first:\n\n```text\npnpm architecture:adopt \u003Cmodule-id> --root \u003Cdir> [--root \u003Cdir2>] --layer \u003Cdomain|app|adapters|ui> [--owner \u003Cgroup>]\n```\n\n`adopt` infers `requires` from the real imports, scaffolds the five artifacts if missing, and registers the module in `architecture-policy.yaml` without touching existing comments. Fill `contract.ts` and `CONTRACT.md` before adding behavior; keep the module's public surface to one intent per method.\n\nFor a new managed module, provide `module.ts`, `contract.ts`, `contract.example.ts`, `contract.test.ts`, and a short `CONTRACT.md`. Keep runtime and persistence details behind the contract. Prefer typed service calls for one-to-one interactions, commands for state changes, and typed events for broadcast facts.\n\nSee [policy-schema.md](references\u002Fpolicy-schema.md), [module-contract.md](references\u002Fmodule-contract.md), and [rule-catalog.md](references\u002Frule-catalog.md) when the change needs their detailed guidance. The [golden-module](references\u002Fgolden-module) fixture is the smallest compliant example.\nSee [ai-guidance.md](references\u002Fai-guidance.md) for the anti-patterns this workflow is designed to prevent and the questions an agent must answer before proposing code.\n",{"name":5,"description":7},"main","cf24e347c4aaf1182ef9fa1f9743a80ab14ff638",".agents\u002Fskills\u002Farchitecture-governance",20,"https:\u002F\u002Fgithub.com\u002FZCodium-project\u002FZCodium","https:\u002F\u002Fzcodium-project.github.io\u002F","https:\u002F\u002Fgithub.com\u002FZCodium-project","zcodium-project.github.io\u002F","Zcode Open Audit Version.","2026-11-13 18:44:38",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add ZCodium-project\u002FZCodium --skill architecture-governance",{"tool":40,"command":41},"bunx","bunx skills add ZCodium-project\u002FZCodium --skill architecture-governance",{"tool":43,"command":44},"pnpm","pnpm dlx skills add ZCodium-project\u002FZCodium --skill architecture-governance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FZCodium-project\u002FZCodium\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Farchitecture-governance\u002FSKILL.md",true,[48,54,58,64,68,72,76,79,83,87,91,95],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"agents\u002Fopenai.yaml","REFERENCE","参考文档",353,"https:\u002F\u002Fgithub.com\u002FZCodium-project\u002FZCodium\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Farchitecture-governance\u002Fagents\u002Fopenai.yaml",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fai-guidance.md",2972,"https:\u002F\u002Fgithub.com\u002FZCodium-project\u002FZCodium\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Farchitecture-governance\u002Freferences\u002Fai-guidance.md",{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fgolden-module\u002Fcontract.example.ts","SCRIPT","脚本",141,"https:\u002F\u002Fgithub.com\u002FZCodium-project\u002FZCodium\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Farchitecture-governance\u002Freferences\u002Fgolden-module\u002Fcontract.example.ts",{"path":65,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fgolden-module\u002FCONTRACT.md",181,"https:\u002F\u002Fgithub.com\u002FZCodium-project\u002FZCodium\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Farchitecture-governance\u002Freferences\u002Fgolden-module\u002FCONTRACT.md",{"path":69,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fgolden-module\u002Fcontract.test.ts",237,"https:\u002F\u002Fgithub.com\u002FZCodium-project\u002FZCodium\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Farchitecture-governance\u002Freferences\u002Fgolden-module\u002Fcontract.test.ts",{"path":73,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fgolden-module\u002Fcontract.ts",57,"https:\u002F\u002Fgithub.com\u002FZCodium-project\u002FZCodium\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Farchitecture-governance\u002Freferences\u002Fgolden-module\u002Fcontract.ts",{"path":77,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":78},"references\u002Fgolden-module\u002Fmodule.ts","https:\u002F\u002Fgithub.com\u002FZCodium-project\u002FZCodium\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Farchitecture-governance\u002Freferences\u002Fgolden-module\u002Fmodule.ts",{"path":80,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fmodule-contract.md",505,"https:\u002F\u002Fgithub.com\u002FZCodium-project\u002FZCodium\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Farchitecture-governance\u002Freferences\u002Fmodule-contract.md",{"path":84,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fpolicy-schema.md",2327,"https:\u002F\u002Fgithub.com\u002FZCodium-project\u002FZCodium\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Farchitecture-governance\u002Freferences\u002Fpolicy-schema.md",{"path":88,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Frule-catalog.md",4843,"https:\u002F\u002Fgithub.com\u002FZCodium-project\u002FZCodium\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Farchitecture-governance\u002Freferences\u002Frule-catalog.md",{"path":92,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Ftroubleshooting.md",1137,"https:\u002F\u002Fgithub.com\u002FZCodium-project\u002FZCodium\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Farchitecture-governance\u002Freferences\u002Ftroubleshooting.md",{"path":96,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":97,"sourceHtmlUrl":98},"scripts\u002Fcontext-package.mjs",718,"https:\u002F\u002Fgithub.com\u002FZCodium-project\u002FZCodium\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Farchitecture-governance\u002Fscripts\u002Fcontext-package.mjs",[100,107,114,121,128,135],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7DBYM2HAMB3K65Q3XET0XWW","plugin-mcp-ping","E2E workspace Plugin skill marker","https:\u002F\u002Fgithub.com\u002FZCodium-project\u002FZCodium\u002Fblob\u002Fmain\u002Fpackages\u002Fdesktop\u002Ftest\u002Fe2e\u002Ffixtures\u002Fplugin-mcp-skill\u002Fe2e-plugin-mcp-ping\u002Fskills\u002Fplugin-mcp-ping\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7DBYCTV753XKE9TRBT8CRSX","zcode-configuration-guide","Use when configuring ZCode's extension resources (MCP servers, slash commands, skills, hooks, and plugins) or instruction files such as AGENTS.md in the ZCode client. Explains where each resource is configured at the user and workspace scope, the discovery order, precedence, and merge rules, plus guidance on which location to choose. Use when someone asks how to add an MCP server, command, skill, hook, plugin, or AGENTS.md instructions, where a configuration file lives, why a configuration is not taking effect, or needs routing to a specific diagnostic skill.","https:\u002F\u002Fgithub.com\u002FZCodium-project\u002FZCodium\u002Fblob\u002Fmain\u002Fapps\u002Fzcode-cli\u002Fpackages\u002Fzcode-guide-plugin\u002Fskills\u002Fzcode-configuration-guide\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":19},"01M7DBY4P7GEEPQZ5VSWCF0YS1","diagnosing-skills","Use to diagnose and fix ZCode skill configuration problems in the ZCode client. Applies when a skill is not discovered, is installed but does not trigger automatically, is shadowed by a higher-precedence skill of the same name, is disabled by configuration, has a SKILL.md frontmatter error, fails to load because its description is too long, or disappears because the plugin providing it is disabled. Provides the discovery order, how to inspect skills in the client, common pitfalls, and a step-by-step localization and repair workflow.","https:\u002F\u002Fgithub.com\u002FZCodium-project\u002FZCodium\u002Fblob\u002Fmain\u002Fapps\u002Fzcode-cli\u002Fpackages\u002Fzcode-guide-plugin\u002Fskills\u002Fdiagnosing-skills\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":19},"01M7DBXS9PAV8Z09309HMYMNPC","diagnosing-plugins","Use to diagnose and fix ZCode plugin and marketplace problems in the ZCode client. Applies when a plugin is not listed, adding a marketplace or installing a plugin fails, a plugin is enabled but its skills or commands are missing, a built-in plugin still appears after being disabled, a plugin is not enabled as expected, a plugin.json manifest has a parse error, a plugin name is invalid, a dependency is unresolved or blocked across marketplaces, or a sensitive configuration value cannot be entered in the interface. Provides the plugin lifecycle, manifest schema, how to manage plugins in the client, and a step-by-step localization and repair workflow.","https:\u002F\u002Fgithub.com\u002FZCodium-project\u002FZCodium\u002Fblob\u002Fmain\u002Fapps\u002Fzcode-cli\u002Fpackages\u002Fzcode-guide-plugin\u002Fskills\u002Fdiagnosing-plugins\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":19},"01M7DBXHJ0G1KZDC405HYQBHB6","diagnosing-mcp","Use to diagnose and fix ZCode MCP (Model Context Protocol) server configuration problems in the ZCode client. Applies when an MCP server will not connect, its tools (mcp__server__tool) do not appear, it shows as disabled or failed, connections time out, a command cannot be found, template variables are not expanded, or a server defined in a configuration file has no effect. Provides configuration locations, how to inspect status in Settings, common pitfalls, and a step-by-step localization and repair workflow.","https:\u002F\u002Fgithub.com\u002FZCodium-project\u002FZCodium\u002Fblob\u002Fmain\u002Fapps\u002Fzcode-cli\u002Fpackages\u002Fzcode-guide-plugin\u002Fskills\u002Fdiagnosing-mcp\u002FSKILL.md",[],[],{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":19},"01M7DBXABP8ZRNM6TFWDJXJH9Z","diagnosing-hooks","Use to diagnose and fix ZCode hook configuration problems in the ZCode client. Applies when a hook does not trigger, an event name is wrong, a matcher does not match a tool name, a script is not executable, template variables are not expanded, a timeout unit is mistaken (seconds versus milliseconds), the command and process field styles are mixed, a hook's JSON output fails validation, a hook blocks the session unexpectedly, or configuration-file hooks are not enabled. Provides configuration sources, the hooks.json schema, how to inspect hooks in the client, and a step-by-step localization and repair workflow.","https:\u002F\u002Fgithub.com\u002FZCodium-project\u002FZCodium\u002Fblob\u002Fmain\u002Fapps\u002Fzcode-cli\u002Fpackages\u002Fzcode-guide-plugin\u002Fskills\u002Fdiagnosing-hooks\u002FSKILL.md",[],[]]