Agent-alchemy lifecycle-hooks
Behavioral rules and lifecycle event handlers for the core-tools package. Defines automated behaviors that trigger at specific points in the agent workflow. (converted from hooks)
git clone https://github.com/sequenzia/agent-alchemy
T=$(mktemp -d) && git clone --depth=1 https://github.com/sequenzia/agent-alchemy "$T" && mkdir -p ~/.claude/skills && cp -r "$T/ported/20260305-085418/core-tools/skills/lifecycle-hooks" ~/.claude/skills/sequenzia-agent-alchemy-lifecycle-hooks-243118 && rm -rf "$T"
ported/20260305-085418/core-tools/skills/lifecycle-hooks/SKILL.mdLifecycle Hooks
This skill defines automated behaviors that trigger at specific points in the agent workflow for the core-tools package.
On before_action
Trigger: Fires before the agent executes any action (file write, shell command, etc.) Applies when: Action matches
Write|Edit|Bash
Auto-approve file operations targeting deep-analysis session and cache directories. This allows the deep-analysis workflow to write session files (checkpoints, findings, cache) without requiring manual approval for each operation.
The implementation logic is in references/auto-approve-da-session.sh. This script:
- Checks if the file operation targets
,.agents/sessions/__da_live__/
, or.agents/sessions/exploration-cache/
directories.agents/sessions/da-*/ - Auto-approves matching operations to enable autonomous session management
- Passes through all other operations to normal permission flow
- Expected input: Action context as JSON on stdin (with
andtool_name
fields)tool_input - Expected output: JSON permission decision or empty (no opinion)
Integration Notes
This skill documents lifecycle automation that was originally implemented as platform-specific hooks. When integrating with a specific agent platform:
- Hook registration: Map the
trigger to the platform's pre-execution hook mechanism (e.g.,before_action
in Claude Code, pre-action middleware in other platforms)PreToolUse - Matcher pattern: The trigger should only fire for file write, file edit, and shell command actions
- Timeout: The approval script should complete within 5 seconds
- Fail-safe behavior: If the script fails or times out, fall through to normal permission flow (never block the agent)
- Path patterns: The script matches against
subdirectories specific to the deep-analysis workflow.agents/sessions/