skills.rest
jasonsie
jasonsieCOMMUNITY
Explore all skills by this author →
GitHub

Hook Development

Validate Claude Code plugin hooks across PreToolUse, PostToolUse, Stop, and SessionStart events.

Updated Aug 23, 2026
Search Tags:#security#validation#event-driven#claude-code#hook#plugin-development#prompt-based
One-click install
npx skills add https://github.com/jasonsie/prompt-dev --skill hook-development-jasonsie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Hook Development
Source: https://github.com/jasonsie/prompt-dev/tree/main/skills/hook-development
Command: npx skills add https://github.com/jasonsie/prompt-dev --skill hook-development-jasonsie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Coordinated, safe automation of Claude Code plugin hooks is hard; developers need a structured approach to validate tool usage, enforce policies, and wire events across the lifecycle.

Core Features & Use Cases

  • Flexible hook types: prompt-based hooks for nuanced, context-aware decisions and command hooks for deterministic checks.
  • Centralized configuration: manage PreToolUse, PostToolUse, Stop, SessionStart, and related events via hooks.json with portable paths.
  • Context & safety tooling: environment loading, logging, and error handling to maintain reliability and security.
  • Use cases include validating tool calls before execution, blocking dangerous operations, and enforcing completion criteria across workflow stages.

Quick Start

Configure a prompt-based PreToolUse hook to review every tool call and validate it using the plugin's test harness.

Frequently Asked Questions about Hook Development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate tool calls before execution in Claude Code?▼

To validate tool calls before execution in Claude Code, configure a PreToolUse hook. This intercepts requests, applies policy enforcement and safety checks, and blocks dangerous operations from running.

What is the difference between prompt-based and command hooks for Claude Code plugins?▼

Prompt-based hooks handle nuanced, context-aware decisions, whereas command hooks execute deterministic checks. Both hook types process JSON I/O to automate context loading and enforce policies across events.

How do I enforce completion criteria across workflow stages using Claude Code hooks?▼

You can enforce completion criteria by wiring Stop and PostToolUse hooks. These lifecycle events execute validation logic against your policies to ensure all workflow requirements are met before proceeding.

Does Claude Code hook development support environment loading and testing?▼

Claude Code hook development supports environment loading, logging, and error handling to maintain reliability. It also includes a test harness to validate prompt-based and command hook behavior safely.

Can I manage PreToolUse, PostToolUse, and SessionStart events in one configuration file?▼

Yes, you can centralize management of PreToolUse, PostToolUse, Stop, and SessionStart events via a hooks.json file. This configuration uses portable paths for consistent event-driven automation across plugins.

Related Skills

Explore More Software Engineering Skills→
JKKN-InstitutionsJKKN-Institutions
1

Hook Development

Define event-driven hooks in hooks.json to govern Claude Code tool usage.

Official
Advanced
atholaathola
326

hook-authoring

Author secure policy-driven hooks for Claude Code and Agent SDK events.

Community
Intermediate
brixtonphambrixtonpham

hook-development

Implement custom Claude Code plugin hooks for events like PreToolUse and PostToolUse.

Community
Advanced
jmolzjmolz

Hook Development

Automate event-driven validation and policy enforcement with Codex hooks.

Community
Advanced