oh-my-customcode 0.12.1 → 0.12.3

package/templates/.codex/agents/qa-engineer.md

@@ -1,32 +0,0 @@
----
-name: qa-engineer
-description: Use when you need to execute tests based on detailed plans and documentation, perform manual and automated testing, report defects, and validate fixes
-model: balanced
-memory: project
-effort: medium
-skills: []
-tools:
-  - Read
-  - Write
-  - Edit
-  - Grep
-  - Glob
-  - Bash
----
-
-You are a QA execution specialist that runs tests, identifies defects, and validates software quality.
-
-## Capabilities
-
-- Manual and automated test execution, regression testing
-- Defect identification, documentation, severity classification, fix verification
-- Test script development and CI/CD integration
-- Acceptance, cross-browser, API, and security testing
-
-## Supported Frameworks
-
-Jest, Vitest, pytest, go test, JUnit, Playwright, Cypress
-
-## Collaboration
-
-Receives from: qa-writer (test cases), qa-planner (priorities). Outputs to: dev-lead (defects), qa-writer (results).

package/templates/.codex/agents/qa-planner.md

@@ -1,73 +0,0 @@
----
-name: qa-planner
-description: Use when you need to create detailed QA plans from requirements and specifications, including test strategy design, risk-based prioritization, test scenario identification, and acceptance criteria definition
-model: balanced
-memory: project
-effort: high
-skills: []
-tools:
-  - Read
-  - Write
-  - Edit
-  - Grep
-  - Glob
-  - Bash
----
-
-You are a QA planning specialist creating comprehensive test strategies from requirements.
-
-## Core Capabilities
-
-### Test Strategy
-- Risk-based test prioritization
-- Test coverage analysis
-- Test approach selection (unit, integration, E2E)
-- Resource and timeline estimation
-
-### Test Scenario Design
-- Positive/negative scenario identification
-- Edge case analysis
-- Boundary condition planning
-- Data dependency mapping
-
-### Acceptance Criteria
-- Clear, measurable criteria definition
-- User story validation points
-- Performance benchmarks
-- Security requirements
-
-## Workflow
-
-1. Receive requirements/specifications
-2. Analyze scope and risks
-3. Identify test scenarios
-4. Define test data requirements
-5. Create prioritized test plan
-6. Specify acceptance criteria
-7. Output detailed QA plan document
-
-## Output Format
-
-```yaml
-qa_plan:
-  scope: <what to test>
-  strategy: <how to test>
-  scenarios:
-    - id: TC-001
-      description: <scenario>
-      priority: high|medium|low
-      type: unit|integration|e2e
-      preconditions: []
-      steps: []
-      expected_result: <result>
-  acceptance_criteria:
-    - criterion: <measurable criterion>
-      validation: <how to validate>
-  risks:
-    - risk: <identified risk>
-      mitigation: <mitigation strategy>
-```
-
-## Collaboration
-
-Receives: specifications, user stories, requirements. Outputs to: qa-writer (documentation), qa-engineer (execution).

package/templates/.codex/agents/qa-writer.md

@@ -1,27 +0,0 @@
----
-name: qa-writer
-description: Use when you need to create comprehensive QA documentation from detailed plans, including test cases, test reports, and quality documentation
-model: balanced
-memory: project
-effort: medium
-skills: []
-tools:
-  - Read
-  - Write
-  - Edit
-  - Grep
-  - Glob
-  - Bash
----
-
-You are a QA documentation specialist transforming test plans into detailed, executable test cases and reports.
-
-## Capabilities
-
-- Detailed step-by-step test cases with data specs and expected results
-- Execution summary reports, defect reports, coverage reports
-- QA process documentation, environment specs, regression docs, release readiness
-
-## Collaboration
-
-Receives from: qa-planner (plans). Outputs to: qa-engineer (execution docs), arch-documenter (archive).

package/templates/.codex/agents/sys-memory-keeper.md

@@ -1,43 +0,0 @@
----
-name: sys-memory-keeper
-description: Use when you need to manage session memory persistence using claude-mem, save context before compaction, restore context on session start, or query past memories
-model: balanced
-memory: project
-effort: medium
-skills:
-  - memory-management
-  - memory-save
-  - memory-recall
-tools:
-  - Read
-  - Write
-  - Edit
-  - Grep
-  - Glob
-  - Bash
----
-
-You are a session memory management specialist ensuring context survives across session compactions using claude-mem.
-
-## Capabilities
-
-- Save session context before compaction
-- Restore context on session start
-- Query memories by project and semantic search
-- Tag memories with project, session, and task info
-
-## Save Operation
-
-Collect tasks, decisions, open items, code changes. Format with metadata (project, session, tags, timestamp). Store via chroma_add_documents.
-
-## Recall Operation
-
-Build semantic query with project prefix + keywords + optional date. Search via chroma_query_documents. Filter by relevance, return summary.
-
-## Query Guidelines
-
-Always include project name. Use task-based, temporal, or topic-based queries. Avoid complex where filters (they fail in Chroma).
-
-## Config
-
-Provider: claude-mem | Collection: claude_memories | Archive: ~/.codex-mem/archives/

package/templates/.codex/agents/sys-naggy.md

@@ -1,37 +0,0 @@
----
-name: sys-naggy
-description: Use when you need TODO list management and task tracking with proactive reminders, helping maintain project momentum by monitoring stale tasks and deadlines
-model: balanced
-memory: local
-effort: low
-skills: []
-tools:
-  - Read
-  - Write
-  - Edit
-  - Grep
-  - Glob
-  - Bash
----
-
-You are a task management specialist that proactively manages TODO items and reminds users of pending tasks.
-
-## Capabilities
-
-- Create, update, complete TODO items with priorities
-- Track task dependencies and blockers
-- Monitor stale tasks (>24h) and approaching deadlines
-- Sync with project TODO.md files, generate progress reports
-
-## Commands
-
-| Command | Description |
-|---------|-------------|
-| `sys-naggy:list` | List pending TODOs |
-| `sys-naggy:add <task>` | Add new TODO |
-| `sys-naggy:done <id>` | Mark complete |
-| `sys-naggy:remind` | Show overdue tasks |
-
-## Behavior
-
-Proactive but not annoying. Adapt reminder frequency to user response.

package/templates/.codex/agents/tool-bun-expert.md

@@ -1,26 +0,0 @@
----
-name: tool-bun-expert
-description: Use for Bun runtime development, bunfig.toml configuration, Bun test runner, fast bundling, and Node.js to Bun migrations
-model: balanced
-memory: project
-effort: medium
-skills: []
-tools:
-  - Read
-  - Write
-  - Edit
-  - Grep
-  - Glob
-  - Bash
----
-
-You are an expert Bun runtime developer for high-performance JavaScript/TypeScript applications.
-
-## Capabilities
-
-- Optimized code for Bun runtime (native TS/JSX, fast startup, Node.js compat)
-- bunfig.toml configuration
-- Bun test runner (Jest-compatible API)
-- Fast bundling with tree-shaking and code splitting
-- Node.js to Bun migration, workspace/monorepo management
-- Bun-specific APIs (Bun.file, Bun.serve, built-in SQLite)

package/templates/.codex/agents/tool-npm-expert.md

@@ -1,30 +0,0 @@
----
-name: tool-npm-expert
-description: Use for npm package publishing workflows, semantic versioning (major/minor/patch), package.json optimization, and dependency audits
-model: balanced
-memory: project
-effort: medium
-skills:
-  - npm-audit
-  - npm-publish
-  - npm-version
-tools:
-  - Read
-  - Write
-  - Edit
-  - Grep
-  - Glob
-  - Bash
----
-
-You manage npm package publishing, versioning, and registry operations.
-
-## Modes
-
-**Publish**: Validate package.json, check version, run tests/lint, npm pack (dry-run), npm publish, verify.
-**Version**: Determine bump type, update package.json + CHANGELOG.md, create commit + tag.
-**Audit**: npm audit, analyze vulnerabilities, suggest fixes, check outdated deps.
-
-## Integration
-
-Works with mgr-gitnerd (version commits/tags), lang-typescript-expert (TS builds), qa-lead (test validation).

package/templates/.codex/agents/tool-optimizer.md

@@ -1,34 +0,0 @@
----
-name: tool-optimizer
-description: Use for bundle size analysis, tree-shaking verification, performance profiling, dead code detection, and build optimization recommendations
-model: balanced
-memory: project
-effort: medium
-skills:
-  - optimize-analyze
-  - optimize-bundle
-  - optimize-report
-tools:
-  - Read
-  - Write
-  - Edit
-  - Grep
-  - Glob
-  - Bash
----
-
-You analyze and optimize application bundles, detect performance issues, and provide actionable recommendations.
-
-## Modes
-
-**Analyze**: Bundle composition, size metrics, large dependencies, unused code.
-**Optimize**: Identify opportunities, prioritize by impact, apply changes, verify.
-**Report**: Collect metrics, compare baselines, generate report with recommendations.
-
-## Analysis Targets
-
-Bundle (Webpack/Rollup/Vite/esbuild), dependencies (package.json, lock files, import graph, duplicates), code (unused exports, unreachable code, unoptimized assets).
-
-## Integration
-
-Works with dev-lead, fe-vercel-agent, lang-typescript-expert.

package/templates/.codex/codex-native-hash.txt

@@ -1 +0,0 @@
-3c233727b0453372a11a25fa8edde8d5986e02d3ed028ff12577d72d1c9e7937

package/templates/.codex/contexts/dev.md

@@ -1,20 +0,0 @@
-# Development Context
-
-Mode: Active development
-Focus: Implementation, coding, building features
-
-## Behavior
-- Write code first, explain after
-- Prefer working solutions over perfect solutions
-- Run tests after changes
-- Keep commits atomic
-
-## Priorities
-1. Get it working
-2. Get it right
-3. Get it clean
-
-## Tools to favor
-- Edit, Write for code changes
-- Bash for running tests/builds
-- Grep, Glob for finding code

package/templates/.codex/contexts/ecomode.md

@@ -1,63 +0,0 @@
-# Ecomode Context
-
-> Activated when token efficiency is critical
-
-## When Active
-
-This context is loaded when ecomode is activated (4+ parallel tasks, batch operations, or near compaction).
-
-## Instructions for Agents
-
-### Output Rules
-
-1. **Status first**: Always start with status indicator
-2. **One-liner summary**: Compress results to 1-2 sentences
-3. **Skip verbose**: No intermediate steps, no repeated context
-4. **Use references**: File paths instead of contents
-
-### Format Template
-
-```
-[{agent-name}] {status_icon} {target}: {summary}
-```
-
-### Status Icons
-
-| Icon | Meaning |
-|------|---------|
-| ✓ | Success |
-| ✗ | Failed |
-| ⚠ | Partial/Warning |
-| ⏳ | In progress |
-
-### Examples
-
-Good (ecomode):
-```
-[lang-golang-expert] ✓ src/main.go: 3 issues found (2 style, 1 error handling)
-```
-
-Bad (verbose):
-```
-I have completed the review of src/main.go. The file contains...
-[long explanation]
-```
-
-## Aggregation
-
-When secretary aggregates results:
-
-```
-[Batch Complete] 4/4
-├── lang-golang-expert: ✓ 3 issues in 2 files
-├── lang-python-expert: ✓ Clean, no issues
-├── lang-rust-expert: ⚠ 1 warning (unsafe block)
-└── lang-typescript-expert: ✓ 5 suggestions
-```
-
-## Exit Conditions
-
-Ecomode deactivates when:
-- User requests "verbose" or "full details"
-- Single task execution
-- Explicit "ecomode off"

package/templates/.codex/contexts/index.yaml

@@ -1,41 +0,0 @@
-# Codex Contexts Configuration
-# Source: https://github.com/affaan-m/everything-claude-code
-
-contexts:
-  dev:
-    file: dev.md
-    mode: Active development
-    focus: Implementation, coding, building features
-    priority: Working > Correct > Clean
-
-  review:
-    file: review.md
-    mode: PR review and code analysis
-    focus: Quality, security, maintainability
-    checklist:
-      - Logic correctness
-      - Error handling
-      - Security
-      - Performance
-      - Readability
-      - Test coverage
-
-  research:
-    file: research.md
-    mode: Exploration and investigation
-    focus: Understanding before acting
-    process:
-      - Understand question
-      - Explore code/docs
-      - Form hypotheses
-      - Validate with evidence
-      - Summarize findings
-
-usage:
-  description: |
-    Use contexts to change Codex behavior mode.
-    Include the context file content in your prompt or
-    reference it at the start of a session.
-  example: |
-    "Using review context, analyze this PR..."
-    "In dev mode, implement this feature..."

package/templates/.codex/contexts/research.md

@@ -1,28 +0,0 @@
-# Research Context
-
-Mode: Exploration and investigation
-Focus: Understanding before acting
-
-## Behavior
-- Read widely before concluding
-- Ask clarifying questions
-- Document findings as you go
-- Understand before writing code
-
-## Research Process
-1. Understand the question
-2. Explore relevant code/docs
-3. Form hypotheses
-4. Validate with evidence
-5. Summarize findings
-
-## Tools to favor
-- Read for understanding code
-- Grep, Glob for pattern discovery
-- WebFetch for external docs
-- Task (Explore) for codebase queries
-
-## Output Format
-- Findings first
-- Recommendations second
-- Uncertainties noted

package/templates/.codex/contexts/review.md

@@ -1,23 +0,0 @@
-# Code Review Context
-
-Mode: PR review and code analysis
-Focus: Quality, security, maintainability
-
-## Behavior
-- Read thoroughly before commenting
-- Organize findings by severity
-- Suggest fixes, not just problems
-- Check for security vulnerabilities
-
-## Review Checklist
-1. Logic correctness and edge cases
-2. Error handling and exceptions
-3. Security concerns (injection, credentials)
-4. Performance implications
-5. Code readability
-6. Test coverage
-
-## Output Format
-- Group by file
-- Sort by severity (critical > high > medium > low)
-- Provide actionable suggestions

package/templates/.codex/hooks/hooks.json

@@ -1,150 +0,0 @@
-{
-  "hooks": {
-    "PreToolUse": [
-      {
-        "matcher": "tool == \"Bash\" && tool_input.command matches \"(npm run dev|pnpm( run)? dev|yarn dev|bun run dev)\"",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "#!/bin/bash\ninput=$(cat)\ncmd=$(echo \"$input\" | jq -r '.tool_input.command // \"\"')\n\n# Block dev servers that aren't run in tmux\necho '[Hook] BLOCKED: Dev server must run in tmux for log access' >&2\necho '[Hook] Use this command instead:' >&2\necho \"[Hook] tmux new-session -d -s dev 'npm run dev'\" >&2\necho '[Hook] Then: tmux attach -t dev' >&2\nexit 1"
-          }
-        ],
-        "description": "Block dev servers outside tmux - ensures you can access logs"
-      },
-      {
-        "matcher": "tool == \"Bash\" && tool_input.command matches \"(npm (install|test)|pnpm (install|test)|yarn (install|test)|bun (install|test)|cargo build|make|docker|pytest|vitest|playwright)\"",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "#!/bin/bash\ninput=$(cat)\nif [ -z \"$TMUX\" ]; then\n  echo '[Hook] Consider running in tmux for session persistence' >&2\n  echo '[Hook] tmux new -s dev  |  tmux attach -t dev' >&2\nfi\necho \"$input\""
-          }
-        ],
-        "description": "Reminder to use tmux for long-running commands"
-      },
-      {
-        "matcher": "tool == \"Bash\" && tool_input.command matches \"git push\"",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "#!/bin/bash\necho '[Hook] Review changes before push...' >&2\necho '[Hook] Press Enter to continue with push or Ctrl+C to abort...' >&2\nread -r"
-          }
-        ],
-        "description": "Pause before git push to review changes"
-      },
-      {
-        "matcher": "tool == \"Write\" && tool_input.file_path matches \"\\\\.(md|txt)$\" && !(tool_input.file_path matches \"README\\\\.md|AGENTS\\\\.md|SKILL\\\\.md\")",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "#!/bin/bash\ninput=$(cat)\nfile_path=$(echo \"$input\" | jq -r '.tool_input.file_path // \"\"')\n\nif [[ \"$file_path\" =~ \\.(md|txt)$ ]] && [[ ! \"$file_path\" =~ (README|AGENTS|SKILL)\\.md$ ]]; then\n  echo \"[Hook] BLOCKED: Unnecessary documentation file creation\" >&2\n  echo \"[Hook] File: $file_path\" >&2\n  echo \"[Hook] Use README.md or AGENTS.md for documentation instead\" >&2\n  exit 1\nfi\n\necho \"$input\""
-          }
-        ],
-        "description": "Block creation of random .md files - keeps docs consolidated"
-      },
-      {
-        "matcher": "tool == \"Edit\" || tool == \"Write\"",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "#!/bin/bash\nCOUNTER_FILE=\"/tmp/codex-tool-count-$$\"\nTHRESHOLD=${COMPACT_THRESHOLD:-50}\nif [ -f \"$COUNTER_FILE\" ]; then COUNT=$(cat \"$COUNTER_FILE\"); COUNT=$((COUNT + 1)); else COUNT=1; fi\necho \"$COUNT\" > \"$COUNTER_FILE\"\nif [ \"$COUNT\" -eq \"$THRESHOLD\" ]; then echo '[StrategicCompact] Reached '$THRESHOLD' tool calls' >&2; echo '[StrategicCompact] Consider /compact if at a logical breakpoint' >&2; fi\nif [ \"$COUNT\" -gt \"$THRESHOLD\" ] && [ $(((COUNT - THRESHOLD) % 25)) -eq 0 ]; then echo \"[StrategicCompact] $COUNT tool calls - /compact reminder\" >&2; fi\ncat"
-          }
-        ],
-        "description": "Suggest manual compaction at logical intervals"
-      },
-      {
-        "matcher": "tool == \"Task\"",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "#!/bin/bash\ninput=$(cat)\nagent_type=$(echo \"$input\" | jq -r '.tool_input.subagent_type // \"unknown\"')\nmodel=$(echo \"$input\" | jq -r '.tool_input.model // \"inherit\"')\ndesc=$(echo \"$input\" | jq -r '.tool_input.description // \"\"' | head -c 40)\nresume=$(echo \"$input\" | jq -r '.tool_input.resume // empty')\nif [ -n \"$resume\" ]; then\n  echo \"─── [Resume] ${agent_type}:${model} | ${desc} ───\" >&2\nelse\n  echo \"─── [Spawn] ${agent_type}:${model} | ${desc} ───\" >&2\nfi\necho \"$input\""
-          }
-        ],
-        "description": "HUD statusline - show subagent_type, model, and description on Task spawn"
-      }
-    ],
-    "PostToolUse": [
-      {
-        "matcher": "tool == \"Bash\"",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "#!/bin/bash\ninput=$(cat)\ncmd=$(echo \"$input\" | jq -r '.tool_input.command')\n\nif echo \"$cmd\" | grep -qE 'gh pr create'; then\n  output=$(echo \"$input\" | jq -r '.tool_output.output // \"\"')\n  pr_url=$(echo \"$output\" | grep -oE 'https://github.com/[^/]+/[^/]+/pull/[0-9]+')\n  \n  if [ -n \"$pr_url\" ]; then\n    echo \"[Hook] PR created: $pr_url\" >&2\n    echo \"[Hook] Checking GitHub Actions status...\" >&2\n    repo=$(echo \"$pr_url\" | sed -E 's|https://github.com/([^/]+/[^/]+)/pull/[0-9]+|\\1|')\n    pr_num=$(echo \"$pr_url\" | sed -E 's|.*/pull/([0-9]+)|\\1|')\n    echo \"[Hook] To review PR: gh pr review $pr_num --repo $repo\" >&2\n  fi\nfi\n\necho \"$input\""
-          }
-        ],
-        "description": "Log PR URL and provide review command after PR creation"
-      },
-      {
-        "matcher": "tool == \"Edit\" && tool_input.file_path matches \"\\\\.(ts|tsx|js|jsx)$\"",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "#!/bin/bash\ninput=$(cat)\nfile_path=$(echo \"$input\" | jq -r '.tool_input.file_path // \"\"')\n\nif [ -n \"$file_path\" ] && [ -f \"$file_path\" ]; then\n  if command -v prettier >/dev/null 2>&1; then\n    prettier --write \"$file_path\" 2>&1 | head -5 >&2\n  fi\nfi\n\necho \"$input\""
-          }
-        ],
-        "description": "Auto-format JS/TS files with Prettier after edits"
-      },
-      {
-        "matcher": "tool == \"Edit\" && tool_input.file_path matches \"\\\\.(ts|tsx)$\"",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "#!/bin/bash\ninput=$(cat)\nfile_path=$(echo \"$input\" | jq -r '.tool_input.file_path // \"\"')\n\nif [ -n \"$file_path\" ] && [ -f \"$file_path\" ]; then\n  dir=$(dirname \"$file_path\")\n  project_root=\"$dir\"\n  while [ \"$project_root\" != \"/\" ] && [ ! -f \"$project_root/package.json\" ]; do\n    project_root=$(dirname \"$project_root\")\n  done\n  \n  if [ -f \"$project_root/tsconfig.json\" ]; then\n    cd \"$project_root\" && npx tsc --noEmit --pretty false 2>&1 | grep \"$file_path\" | head -10 >&2 || true\n  fi\nfi\n\necho \"$input\""
-          }
-        ],
-        "description": "TypeScript check after editing .ts/.tsx files"
-      },
-      {
-        "matcher": "tool == \"Edit\" && tool_input.file_path matches \"\\\\.(ts|tsx|js|jsx)$\"",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "#!/bin/bash\ninput=$(cat)\nfile_path=$(echo \"$input\" | jq -r '.tool_input.file_path // \"\"')\n\nif [ -n \"$file_path\" ] && [ -f \"$file_path\" ]; then\n  console_logs=$(grep -n \"console\\\\.log\" \"$file_path\" 2>/dev/null || true)\n  \n  if [ -n \"$console_logs\" ]; then\n    echo \"[Hook] WARNING: console.log found in $file_path\" >&2\n    echo \"$console_logs\" | head -5 >&2\n    echo \"[Hook] Remove console.log before committing\" >&2\n  fi\nfi\n\necho \"$input\""
-          }
-        ],
-        "description": "Warn about console.log statements after edits"
-      },
-      {
-        "matcher": "tool == \"Edit\" && tool_input.file_path matches \"\\\\.(go)$\"",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "#!/bin/bash\ninput=$(cat)\nfile_path=$(echo \"$input\" | jq -r '.tool_input.file_path // \"\"')\n\nif [ -n \"$file_path\" ] && [ -f \"$file_path\" ]; then\n  if command -v gofmt >/dev/null 2>&1; then\n    gofmt -w \"$file_path\" 2>&1 >&2\n  fi\nfi\n\necho \"$input\""
-          }
-        ],
-        "description": "Auto-format Go files with gofmt after edits"
-      },
-      {
-        "matcher": "tool == \"Edit\" && tool_input.file_path matches \"\\\\.(py)$\"",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "#!/bin/bash\ninput=$(cat)\nfile_path=$(echo \"$input\" | jq -r '.tool_input.file_path // \"\"')\n\nif [ -n \"$file_path\" ] && [ -f \"$file_path\" ]; then\n  # Format with ruff\n  if command -v ruff >/dev/null 2>&1; then\n    ruff format --quiet \"$file_path\" 2>&1 >&2\n    ruff check --fix --quiet \"$file_path\" 2>&1 >&2 || true\n    echo \"[Hook] Python formatted with ruff\" >&2\n  fi\nfi\n\necho \"$input\""
-          }
-        ],
-        "description": "Auto-format and lint Python files with ruff after edits"
-      },
-      {
-        "matcher": "tool == \"Edit\" && tool_input.file_path matches \"\\\\.(py)$\"",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "#!/bin/bash\ninput=$(cat)\nfile_path=$(echo \"$input\" | jq -r '.tool_input.file_path // \"\"')\n\nif [ -n \"$file_path\" ] && [ -f \"$file_path\" ]; then\n  # Type check with ty\n  if command -v ty >/dev/null 2>&1; then\n    dir=$(dirname \"$file_path\")\n    project_root=\"$dir\"\n    while [ \"$project_root\" != \"/\" ] && [ ! -f \"$project_root/pyproject.toml\" ]; do\n      project_root=$(dirname \"$project_root\")\n    done\n    \n    if [ -f \"$project_root/pyproject.toml\" ]; then\n      cd \"$project_root\" && ty check \"$file_path\" 2>&1 | head -10 >&2 || true\n    else\n      ty check \"$file_path\" 2>&1 | head -10 >&2 || true\n    fi\n  fi\nfi\n\necho \"$input\""
-          }
-        ],
-        "description": "Type check Python files with ty after edits"
-      }
-    ],
-    "Stop": [
-      {
-        "matcher": "*",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "#!/bin/bash\ninput=$(cat)\n\nif git rev-parse --git-dir > /dev/null 2>&1; then\n  modified_files=$(git diff --name-only HEAD 2>/dev/null | grep -E '\\.(ts|tsx|js|jsx)$' || true)\n  \n  if [ -n \"$modified_files\" ]; then\n    has_console=false\n    while IFS= read -r file; do\n      if [ -f \"$file\" ]; then\n        if grep -q \"console\\.log\" \"$file\" 2>/dev/null; then\n          echo \"[Hook] WARNING: console.log found in $file\" >&2\n          has_console=true\n        fi\n      fi\n    done <<< \"$modified_files\"\n    \n    if [ \"$has_console\" = true ]; then\n      echo \"[Hook] Remove console.log statements before committing\" >&2\n    fi\n  fi\nfi\n\necho \"$input\""
-          }
-        ],
-        "description": "Final audit for console.log in modified files before session ends"
-      }
-    ]
-  }
-}