How does the skill handle script failures?

The skill captures exit codes and output for every script; it can be configured to stop the workflow immediately upon failure or continue to the next hook.

What types of hooks are supported?

The skill supports three types: 'document' (markdown files for the LLM to follow), 'script' (shell scripts with timeouts), and 'skill' (invoking other specialized capabilities).

What is a FABER hook?

A FABER hook is a task triggered at the boundary of a development phase (e.g., pre_build or post_architect) to automate checks, documentation reading, or script execution.

Can I run multiple hooks at once?

Yes, using the 'execute-all' operation, the skill will sequence and run every hook configured for a specific phase boundary in order.

Are there safety measures for script execution?

Yes, the skill validates script existence and permissions, executes within a defined timeout period, and uses structured JSON for safe context passing.

Faber Hooks

Name: Faber Hooks
Author: fractary

byfractary

•

Productivity & Workflow

Manages and executes automated workflow hooks at critical phase boundaries within the FABER development lifecycle.

About

Faber Hooks is a specialized utility designed to orchestrate automation within the FABER methodology by triggering actions at specific phase transitions, such as pre-architecting or post-building. It enables developers to integrate shell scripts, documentation checks, and other Claude skills directly into their workflow, ensuring that quality gates and standardized procedures are followed automatically. By providing structured validation and execution of phase-specific hooks, this skill streamlines complex development cycles and reduces manual overhead during project transitions.

Key Features

Execution of individual hooks or aggregated boundary sequences
Supports document, script, and skill-based hook types
Automated hook validation with detailed error reporting
Structured JSON output for seamless agent interaction
Pre-defined boundaries for the entire FABER lifecycle (Frame to Release)
2 GitHub stars

Use Cases

Running automated validation scripts after the architecture phase to verify technical specs
Triggering secondary skills like changelog updates automatically during the release phase
Enforcing manual checklists by prompting the agent to read specific documentation before project framing

About

Key Features

Execution of individual hooks or aggregated boundary sequences
Supports document, script, and skill-based hook types
Automated hook validation with detailed error reporting
Structured JSON output for seamless agent interaction
Pre-defined boundaries for the entire FABER lifecycle (Frame to Release)
2 GitHub stars

Use Cases

Running automated validation scripts after the architecture phase to verify technical specs
Triggering secondary skills like changelog updates automatically during the release phase
Enforcing manual checklists by prompting the agent to read specific documentation before project framing