create-hook

Included with Lifetime

$97 forever

Create or update Codex hooks for global or project scope by asking for scope and hook type when ambiguous, then writing the hook config, scripts, and any required feature flag config.

Writing & Docs

What this skill does


# Create Hook

Use when the user wants to add Codex hooks and explains the behavior they want.

## Workflow

1. Determine scope.
   - If the user says `global`, use the personal/home scope.
   - If the user says `project`, use the repo scope.
   - If scope is missing or unclear, ask: `Should this be global or project-scoped?`

2. Determine hook type.
   - If the event is missing or unclear, ask which hook they want:
     - `SessionStart`
     - `UserPromptSubmit`
     - `PreToolUse`
     - `PostToolUse`
     - `Stop`
   - If the user wants more than one, keep them separate unless they explicitly want shared behavior.

3. Determine behavior.
   - Ask what the hook should do if the intent is not already clear.
   - Prefer the smallest deterministic script that satisfies the request.

4. Write the hook files in the chosen scope.
   - Global: `~/.codex/hooks.json` and `~/.codex/hooks/`
   - Project: `<repo>/.codex/hooks.json` and `<repo>/.codex/hooks/`
   - Keep script paths explicit and relative where practical.

5. Enable the feature flag if the target Codex build still gates hooks.
   - Set `[features] codex_hooks = true` in the relevant `config.toml`.

6. Keep the hook output clear.
   - Use `statusMessage` for a short visible signal.
   - For logging hooks, write to a repo-local or home-local log file.
   - For blocking hooks, return a nonzero exit only when the hook should actually stop the tool.

7. Verify the result.
   - Run a command that should trigger the hook.
   - Confirm the log, output, or blocking behavior matches the requested scope and event.

## Practical defaults

- Use `PreToolUse` for prevention.
- Use `PostToolUse` for logging, formatting, or test follow-up.
- Use `UserPromptSubmit` for prompt shaping and injected context.
- Use `SessionStart` for startup context.
- Use `Stop` for end-of-turn checks.

Files: 3

Size: 3.0 KB

Complexity: 17/100

Category: Writing & Docs

Source: https://github.com/am-will/codex-skills/tree/main/skills/create-hook

Related in Writing & Docs

jax-development

Included

Use this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.

Writing & Docsscripts

nature-article-writer

Included

Drafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.

Writing & Docsscripts

deckrd

Included

Document-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.

Writing & Docsscripts

clinical-decision-support

Included

Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.

Writing & Docsscripts

handling-sf-data

Included

Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).

Writing & Docsscripts

accelint-ac-to-playwright

Included

Convert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.

Writing & Docsscripts