Files
gstack/hosts/codex/hooks/codex-skill-route-hook.ts
T
Garry Tanandcapy-ai[bot] 944b41e24d Codex gets gstack's skill routing hint and destructive-command check (GST-3172) (#4512)
`./setup --host codex` now adds gstack's skill-routing hint and
destructive-command check to Codex's `~/.codex/hooks.json`, next to your
own hooks, so Codex users get the same guardrails Claude Code users
have.

Codex runs a hook only after you trust it, so nothing fires until you
accept gstack's hooks at Codex's startup prompt or in `/hooks`;
`gstack-doctor` shows whether you have.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Review-Finding: p1/red-team#1 reader=red-team
2026-11-19 11:09:11 +00:00

12 lines
659 B
TypeScript
Executable File

#!/usr/bin/env -S bun --no-env-file --config=/dev/null
/**
* codex-skill-route-hook — the skill-routing hook on Codex (GST-3172). The same UserPromptSubmit hook as Claude
* Code's (hosts/claude/hooks/skill-route-hook.ts) with host codex: it scans ${CODEX_HOME:-~/.codex}/skills, names
* skills as Codex does (gstack-review), words the hint for Codex, and never routes a prompt that starts with `$`
* (a Codex skill mention) or `/`. Same switch (skill_routing), same deadline, same trace log.
* Docs: docs/skill-routing-and-contracts.md#codex.
*/
import { runSkillRouteHook } from '../../claude/hooks/skill-route-hook.ts';
runSkillRouteHook('codex');