codex-hook-emulation

Emulate Claude Code hooks in Codex workflows with deterministic scripts.

5|2|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/Tx1207/hello-scholar --skill codex-hook-emulation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-hook-emulation
Source: https://github.com/Tx1207/hello-scholar/tree/main/skills/core/codex-hook-emulation
Command: npx skills add https://github.com/Tx1207/hello-scholar --skill codex-hook-emulation

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Codex Hook Emulation solves the lack of a native hook runtime in Codex by providing a deterministic, script-driven workflow that maps Claude Code hooks to Codex-native actions, enabling safe session management, guarded operations, and auditable records within a repository.

Core Features & Use Cases

  • Deterministic hook mapping: Map Claude Code hooks to Codex actions with a stable, script-driven workflow.
  • Lifecycle guidance: Use a clear sequence (SessionStart, Track-Intent, Track-Change, Post-Edit, Session-End) to capture decisions, edits, and closeouts.
  • Guardrails and bootstrap: Preflight checks guard risky commands and post-edit prompts verify meaningful edits; supports Obsidian-memory bootstrap when bound.
  • Repositories and memory integration: Outputs project-memory hints and bootstrap prompts for unbound repos to help bootstrap workflows.

Quick Start

Activate the codex-hook-emulation skill to start a session and exercise the hook workflow (session-start, preflight, track-intent, post-edit, and session-end) in your repository.

Frequently Asked Questions about codex-hook-emulation

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

FAQPage Schema
How do I emulate Claude Code hooks inside Codex sessions?

A deterministic helper script provides safe workflow emulation by mapping Claude Code hooks to Codex-native actions. It coordinates session start, preflight guardrails, post-edit validation, and session wrap-up across high-risk operations.

What is the hook lifecycle sequence for Codex workflow coordination?

The hook lifecycle sequence for Codex workflow coordination is SessionStart, Track-Intent, Track-Change, Post-Edit, and Session-End. This deterministic sequence captures decisions, edits, and closeouts to maintain auditable records.

Can I use preflight guardrails for high-risk operations in Codex?

Preflight guardrails protect high-risk operations in Codex by checking commands before execution. Post-edit validation prompts also verify meaningful edits to ensure safe session management within the repository.

Does Codex hook emulation work with Obsidian project memory?

Codex hook emulation supports optional Obsidian project memory bootstrap when bound. For unbound repositories, it outputs project-memory hints and bootstrap prompts to help initialize workflows.

How to start a session with codex-hook-emulation?

Activate the codex-hook-emulation skill to start a session and exercise the hook workflow. The deterministic helper script coordinates session-start, preflight, track-intent, post-edit, and session-end events in your repository.

What are the limitations of script-driven hook emulation in Codex?

Script-driven hook emulation in Codex lacks a native hook runtime, requiring a deterministic helper script for execution. It relies on manual lifecycle mapping rather than built-in event triggers for session management.