What events can I trigger with a registered hook?

The skill supports a wide range of triggers including on_file_edit, on_file_save, on_commit, on_push, on_tool_use, on_agent_start, and on_workflow_end.

What is the difference between hook.define and hook.register?

hook.define is used for immediate, ad-hoc hook creation in development environments, while hook.register is designed for production use, requiring a formal YAML manifest and adding it to a versioned registry for team-wide enforcement.

Does this skill support blocking operations?

Yes, you can configure hooks with a 'blocking' flag. If a blocking hook fails its validation or command, it will stop the triggering operation (like a commit) from proceeding.

Can I use Hook Register in my CI/CD pipeline?

Yes, it is specifically designed to be used in CI/CD workflows (like GitHub Actions) to validate all hook manifests in a repository before they are officially registered or deployed.

Hook Register

Name: Hook Register
Author: epieczko

byepieczko

Security & Testing

Validates and registers version-controlled hook manifests to automate governance and enforcement within the Betty infrastructure.

About

Hook Register is a specialized skill designed to formalize the lifecycle of automated hooks by validating YAML manifests and adding them to a centralized, versioned registry. Unlike ad-hoc hook creation, this skill ensures that all triggers—ranging from file edits to git commits—adhere to a strict schema and undergo a formal review process, making it essential for teams implementing enterprise-grade governance and automated validation workflows in Claude Code.

Key Features

Comprehensive schema validation for hook manifests
Version-controlled hook management via a centralized registry
Support for multiple event triggers like on_commit and on_file_save
Automated conflict detection for hook naming and versioning
Seamless integration with CI/CD pipelines for automated hook verification
0 GitHub stars

Use Cases

Standardizing security and audit logging across all tool usage
Implementing organization-wide API compliance checks on every file edit
Automating breaking change detection during the git commit process

About

Key Features

Comprehensive schema validation for hook manifests
Version-controlled hook management via a centralized registry
Support for multiple event triggers like on_commit and on_file_save
Automated conflict detection for hook naming and versioning
Seamless integration with CI/CD pipelines for automated hook verification
0 GitHub stars

Use Cases

Standardizing security and audit logging across all tool usage
Implementing organization-wide API compliance checks on every file edit
Automating breaking change detection during the git commit process