SessionStart

{
  "SessionStart": [
    {
      "hooks": [
        {
          "type": "command",
          "command": "git",
          "args": [
            "-c",
            "alias.codexspec-commit-guidance=!printf '%s\\n' '<!-- CODEXSPEC COMMITS START -->\n## Commit Messages\n\nBefore creating an authorized Git commit, invoke `/codexspec:commit-staged` to analyze staged\nchanges and generate the message. This applies in plain conversation and SDD\nworkflows, including auto-dev feature commits and blueprint commits. Command\navailability alone is not an invocation.\n\nThe calling workflow prepares staging. `commit-staged` must not choose or stage\nfiles, and must not describe unstaged changes or conversation-only intent. Use a\nbody when needed to cover material staged changes accurately and completely.\n\nFor helper-owned commits, prepare the helper'\"'\"'s explicit index first, invoke\n`/codexspec:commit-staged -p` against that index, and pass the full message and analyzed tree\nto the helper'\"'\"'s finalization action. Keep ownership, path, locking, and recovery\nchecks. If content changes, prepare and analyze again before committing; never\nfall back to a fixed message or direct Git execution to bypass a failed check.\nThis rule does not grant authorization to stage, commit, or push.\n<!-- CODEXSPEC COMMITS END -->\n\n<!-- CODEXSPEC SPECS START -->\n## CodexSpec Historical Specs\n\nBefore substantive requirements, behavior, design, implementation, debugging, or\nreview judgments, actively recall relevant history under `.codexspec/specs/`.\nThis applies in ordinary conversation and SDD workflows. Prepare background before\nquestioning the user. Purely mechanical edits, such as spelling or formatting\nwith no substantive judgment, may omit recall.\n\nSelect related features by the task'\"'\"'s capabilities, affected modules, interfaces,\nand terminology; use directory names, artifact headings, and targeted text search\nto find candidates. Read relevant requirements and follo