What kind of actions can hook rules perform?

Rules can deny or allow operations, log messages, inject context into the conversation, warn the user, or even modify tool inputs via scripts.

Do I need to write code to create these hooks?

No, hook rules are written in TOML using a Python-like expression engine, allowing for sophisticated logic without custom software development.

Where are hook rules stored?

They are typically defined in a project's .oaps/hooks.toml file or distributed through OAPS plugins.

What is an OAPS hook rule?

A hook rule is a declarative automation in OAPS that monitors Claude Code events (like tool use) and executes actions based on defined conditions.

How do I test my hook rules before deployment?

This skill includes a dedicated test workflow that creates mock event contexts to verify if your rules match and execute as expected.

OAPS Hook Rule Writing

Name: OAPS Hook Rule Writing
Author: tbhb

bytbhb

Seguridad y Pruebas

Streamlines the creation, debugging, and management of automated guardrails and workflows for the OAPS planning system.

Acerca de

This skill provides specialized guidance for developing hook rules within the Overengineered Agentic Planning System (OAPS). It enables developers to implement declarative, TOML-based automation that responds to Claude Code events, such as tool usage or session starts. By offering structured workflows for brainstorming, writing, and testing, the skill helps enforce project standards, prevent dangerous operations through safety guardrails, and enhance observability through automated logging and context injection.

Características Principales

Step-by-step guidance for writing and validating hook rule syntax
0 GitHub stars
Built-in reference access for events, expressions, and action types
Automated brainstorming for project-specific guardrails and workflows
Comprehensive review of existing hooks to identify priority conflicts
Testing framework to simulate event contexts and debug rule logic

Casos de Uso

Auditing agent behavior by logging specific tool outputs and session events
Automatically injecting project context when modifying sensitive configuration files
Preventing destructive bash commands by blocking specific tool inputs

Acerca de

Características Principales

Step-by-step guidance for writing and validating hook rule syntax
0 GitHub stars
Built-in reference access for events, expressions, and action types
Automated brainstorming for project-specific guardrails and workflows
Comprehensive review of existing hooks to identify priority conflicts
Testing framework to simulate event contexts and debug rule logic

Casos de Uso

Auditing agent behavior by logging specific tool outputs and session events
Automatically injecting project context when modifying sensitive configuration files
Preventing destructive bash commands by blocking specific tool inputs