Menu
Use when asked to create or revise a LazyAI hook policy so runtime enforcement stays objective, generated, and tool-specific.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when debugging a failing test, broken build, runtime error, or unexpected system behavior. Drives hypothesis-based investigation, root-cause fixes, verification, and reusable learning capture.
Use when a claim, plan, spec, doc, or design must be attacked against source evidence before implementation or approval. Uses write tools, shell execution, and may spawn subagents. Invoke with enable_write_tools=true and enable_subagent_tools=true.
Use when fixing broken behavior and the priority is reproduce, root cause, regression proof, and the smallest safe repair. Uses write tools, shell execution, and may spawn subagents. Invoke with enable_write_tools=true and enable_subagent_tools=true.
Use when reviewing code changes with explicit stage, target, and focus so own-code checks and others’ PR reviews stay distinct but share one contract. Uses write tools, shell execution, and may spawn subagents. Invoke with enable_write_tools=true and enable_subagent_tools=true.
Use when the deliverable is docs or reference material and every claim must stay tied to observed behavior or cited source evidence. Uses write tools, shell execution, and may spawn subagents. Invoke with enable_write_tools=true and enable_subagent_tools=true.
Use when adding or changing product behavior that must ship with explicit purpose, scenarios, and verification. Uses write tools, shell execution, and may spawn subagents. Invoke with enable_write_tools=true and enable_subagent_tools=true.
| name | create-hook |
| description | Use when asked to create or revise a LazyAI hook policy so runtime enforcement stays objective, generated, and tool-specific. |
Use this skill when the user asks to:
Do not use when a normal markdown rule is enough and no runtime enforcement is needed.
A shipped LazyAI hook starts with one policy source. In this repository that source is packages/cli/library/hooks/<name>.md. Generated shell scripts, JSON descriptors, and OpenCode plugins are outputs, not authoring locations.
lazyai-cli compile plus lazyai-cli doctor in a consuming project, or go test ./packages/cli/... plus go build ./packages/cli/... when changing LazyAI's embedded hook library or adapters.PreToolUse / PostToolUse map to direct hook events..opencode/plugins/..gemini/settings.json plus shell hooks only.