codebase-index 1.6.0__tar.gz

codebase_index-1.6.0/.claude/skills/codebase-index/.skill_version

@@ -0,0 +1 @@
+1.6.0

codebase_index-1.6.0/.claude/skills/codebase-index/SKILL.md

@@ -0,0 +1,198 @@
+---
+name: codebase-index
+description: Use this skill before answering questions about a repository's architecture, implementation locations, symbols, references, dependencies, refactoring impact, data flow, bugs, or where something is implemented. It searches a local hybrid codebase index so Claude reads only the most relevant files instead of scanning the entire project.
+allowed-tools: Bash(python -m codebase_index *), Bash(python3 -m codebase_index *), Bash(codebase-index *), Bash(cbx *), Read, Grep, Glob
+---
+
+# Codebase Index
+
+Use this skill first for codebase questions.
+
+Never scan the entire repository before searching the index.
+
+## When to use
+
+Invoke this skill **before reading any files** when the user asks about this project's code:
+
+- "where is X implemented" / "find X" / "locate the X function"
+- "how does X work" / "explain the X flow"
+- "what breaks if I change X" / "what depends on X" (impact analysis)
+- "who calls X" / "references to X"
+- "trace the data flow of X"
+- "why is this error happening" (error/stack trace)
+- "explain the architecture" / "give me an overview"
+- Any question about symbols, files, dependencies, or refactoring scope
+
+Do **not** use it for: editing files, running the application, or non-code questions.
+
+## How to call the CLI
+
+Use the `codebase-index` CLI directly, or the bundled `cbx` wrapper:
+
+```bash
+codebase-index search "$QUERY" --json
+```
+
+Pick the subcommand by intent:
+
+| User intent | Command |
+|---|---|
+| "how does X work" / "explain X" / "walk me through" | `codebase-index explain "$QUERY" --json` |
+| overview / architecture / "map the codebase" | `codebase-index architecture --json` |
+| general / unsure | `codebase-index search "$QUERY" --json` |
+| keyword / "where is" | `codebase-index search "$QUERY" --json` |
+| a specific symbol name | `codebase-index symbol "<name>" --json` |
+| "who calls / references" | `codebase-index refs "<name>" --json` |
+| "what breaks if I change" | `codebase-index impact "<file-or-symbol>" --json` |
+| "how is X connected to Y" / dependency path | `codebase-index path "<A>" "<B>" --json` |
+| "what is X" / describe a symbol's role | `codebase-index describe "<name>" --json` |
+| visual graph / "open graph" (for the human, not for you to read) | `codebase-index graph "<file-or-symbol>" --open` |
+
+`architecture` returns the codebase map computed at index time — detected modules
+(communities), god nodes (most-connected symbols), surprising cross-module links,
+and suggested questions. Reach for it on "give me an overview" / "where do I
+start" questions instead of a broad `explain`.
+
+`path "A" "B"` returns the shortest dependency/call chain between two symbols or
+files; `describe "X"` returns a node card (definition, callers, callees,
+in/out degree, module, god-node rank). Both annotate edges with a `confidence`
+(`extracted` exact, `inferred` heuristic, `ambiguous` unresolved) — treat a path
+or callee list that leans on `inferred`/`ambiguous` edges as less certain.
+
+The `graph` command renders an HTML dependency graph for a person to look at —
+it is not a retrieval packet. Use it only when the user explicitly wants a visual
+graph; for "what depends on X" answer from `impact`/`refs` instead. In a headless
+session prefer `--output <path>` over `--open`. `--format graphml|dot|neo4j`
+exports the graph for external tools (Gephi/yEd, Graphviz, Neo4j) instead of HTML.
+
+`explain` has a higher default token budget (2200) and HOW_IT_WORKS intent weights — use it whenever the question is about understanding behavior or flow.
+
+For `search`, pick a `--mode` when the intent is clear:
+- `--mode symbol` — pure symbol lookups (faster, no FTS noise)
+- `--mode fts` — text/keyword queries where symbol names don't matter
+- `--mode hybrid` — default; best for mixed queries
+- `--mode vector` — semantic / near-synonym queries ("where do we rate-limit
+  requests" without the exact words). Requires opt-in embeddings; falls back with
+  a clear message when they are not enabled. `hybrid` already blends vectors in
+  when embeddings are on, so reach for `vector` only for pure-semantic recall.
+
+Natural-language kind words such as `method`, `function`, `class`, `interface`,
+`enum`, and `type` constrain the symbol retriever inside `search`.
+
+Use `--json` for programmatic parsing; omit for human-readable output.
+Search/read commands auto-build the index when it is missing; still check
+freshness and run `update`/`index` when responses report stale data.
+
+## Step-by-step workflow
+
+1. **Query the index** using the appropriate subcommand for `$QUERY`.
+2. **Check index freshness** in the response:
+   - `index.exists: false` → run `codebase-index index` first, then re-query.
+   - `index.stale: true`, `files_changed_since_build < 20` → run `codebase-index update`, then re-query.
+   - `index.stale: true`, `files_changed_since_build ≥ 20` → run `codebase-index index` (full rebuild).
+   - Otherwise proceed with results.
+3. **Read ONLY the `recommended_reads`** — use the Read tool with `offset`/`limit` to read the exact line ranges returned. Do not open whole files.
+4. **Answer** with file:line citations (e.g., `src/auth/token.py:88-134`).
+5. **Fallback** only if confidence is low or results are empty (see below).
+
+## Token-budgeted output interpretation
+
+The index returns a **ranked retrieval packet** with:
+
+- `rank` — result position (start with 1-3)
+- `path` — file path
+- `line_start` / `line_end` — exact line range to read
+- `symbols` — symbols found in this range
+- `score` — relevance score
+- `reason` — why this result ranked (e.g., "exact symbol match, 4 callers")
+- `snippet` — compact code excerpt (may already answer the question); `null` means budget was spent — read via `recommended_reads` instead
+- `skeletonized` — when `true`, the `snippet` is a **focus skeleton**: import/signature/class lines and the line(s) matching your query are kept, while function bodies collapse to a marker like `... 24 lines elided (read 88-134)`. Read that line range (or the result's `line_start`/`line_end`) when you need a full body.
+- `elided_lines` — how many source lines the skeleton folded away (`0` when not skeletonized).
+
+Top-level fields:
+
+- `recommended_reads` — the precise `{path, line_start, line_end}` list to open next. This is your read plan.
+- `confidence` — `high` (answer directly), `medium` (read + optionally confirm with one Grep), `low` (use fallback).
+- `fallback_suggestions` — ripgrep patterns and paths to try if the index is weak.
+- `intent` / `mode` — how the query was classified and which retrievers ran;
+  useful to sanity-check a weak result (e.g. a "how does X work" question that
+  resolved to a bare symbol lookup may need `explain` instead).
+- `pagination` — present only when more results exist than fit the page. It
+  reports `has_more` and `next_offset`. To page, re-run `search` with
+  `--offset <next_offset>` (e.g. `search "query" --limit 10 --offset 10`). Prefer
+  refining with a more specific subcommand or raising `--token-budget` first —
+  page only when the top results genuinely miss the answer.
+- `coverage` (on `refs`/`impact` only) — graph-completeness signal. Dependency
+  edges (imports/inheritance) are extracted only for fully supported languages.
+  When `coverage.partial` is `true` (the symbol/file is in a Tier-B language such
+  as Lua), an **empty or short `refs`/`impact` result is inconclusive** — it may
+  just be unanalyzed, not absent. Confirm with a Grep before concluding "nothing
+  references this". `coverage.languages` lists the affected languages.
+
+## Token efficiency rules
+
+- Trust the index. Read the **fewest** files needed — start with rank 1-3 only.
+- Read **line ranges**, not whole files. Use `line_start`/`line_end` with Read's `offset`/`limit`.
+- The `snippet` may already answer the question — re-read only if you need more context.
+- Prefer `search`/`symbol`/`refs`/`impact`/`explain` over manual Grep/Glob — those are expensive fallbacks, not step 1.
+- Don't re-run the query with trivially reworded text; refine with a different subcommand instead.
+- For broad questions (`confidence: low`, architecture, data-flow), raise the budget: `--token-budget 3000`.
+- Test files are demoted in ranking by default. Include "test" in the query to surface them.
+- Snippets are skeletonized by default to fit more results in the budget. The matched line is always preserved; pass `--raw` (CLI) or `raw: true` (MCP) on the rare occasion you need full bodies inline instead of reading the cited line range.
+
+## Fallback behavior
+
+Fall back to built-in search **only** when: results are empty, `confidence` is `low`, or the user asks for something the index clearly doesn't cover.
+
+0. If confidence is consistently low across queries, run diagnostics first:
+   ```bash
+   codebase-index stats --json    # per-language file/symbol counts + graph tier
+   codebase-index doctor          # surface config or security issues
+   ```
+   Low symbol counts for a language may mean the index needs a full rebuild: `codebase-index index`.
+   In `stats`, each language carries `graph: full|partial` (and `doctor` reports a
+   `graph_coverage` finding): `partial` (Tier-B) means `refs`/`impact` lack
+   import/inheritance edges for that language — treat empty results there as
+   inconclusive.
+
+1. Use `fallback_suggestions.ripgrep` patterns from the response via Grep.
+2. If still nothing, Glob for likely paths, then Grep within them.
+3. As a last resort, broaden the search — but tell the user the index was weak here (it may need a rebuild: `codebase-index index`).
+
+Never start with a full-repo scan when the index exists and is fresh.
+
+## Examples
+
+```bash
+# "how does the auth flow work?"
+codebase-index explain "auth flow" --json
+
+# "explain the overall architecture" / "where do I start" — modules, god nodes
+codebase-index architecture --json
+
+# "where is auth token refresh implemented?"
+codebase-index search "auth token refresh" --json
+
+# "what breaks if I change the User model?"
+codebase-index impact "User" --json
+
+# "who calls send_email?"
+codebase-index refs "send_email" --json
+
+# "find the AuthService class"
+codebase-index symbol "AuthService" --json
+
+# precise symbol search (faster, no FTS noise)
+codebase-index search "AuthService" --mode symbol --json
+
+# "how is the API layer connected to the database?"
+codebase-index path "ApiController" "Database" --json
+
+# "what is the Database class and how is it used?"
+codebase-index describe "Database" --json
+
+# generate and open an HTML graph around a file or symbol
+codebase-index graph "User" --direction both --depth 2 --open
+```
+
+Then Read only the returned line ranges and answer with citations.

codebase_index-1.6.0/.claude/skills/codebase-index/examples/hooks/settings.json

@@ -0,0 +1,16 @@
+{
+  "hooks": {
+    "PostToolUse": [
+      {
+        "matcher": "Edit|Write|MultiEdit",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "codebase-index update --quiet >/dev/null 2>&1 &",
+            "timeout": 5
+          }
+        ]
+      }
+    ]
+  }
+}

codebase_index-1.6.0/.claude/skills/codebase-index/scripts/cbx

@@ -0,0 +1,25 @@
+#!/usr/bin/env bash
+# Thin, safe wrapper around the installed `codebase-index` CLI.
+# - Resolves the binary (prefers one on PATH; falls back to `python -m codebase_index`).
+# - Whitelists subcommands so the skill can never invoke destructive ones (clean/init/watch).
+set -euo pipefail
+
+ALLOWED="search explain symbol refs impact graph stats doctor update index"
+
+sub="${1:-}"
+case " $ALLOWED " in
+  *" ${sub} "*) : ;;
+  *)
+    echo "cbx: refusing subcommand '${sub}'. Allowed: ${ALLOWED}" >&2
+    exit 2
+    ;;
+esac
+
+if python -c "import codebase_index" >/dev/null 2>&1; then
+  exec python -m codebase_index "$@"
+elif command -v codebase-index >/dev/null 2>&1; then
+  exec codebase-index "$@"
+else
+  echo "cbx: codebase_index is not importable and codebase-index is not on PATH" >&2
+  exit 127
+fi

codebase_index-1.6.0/.claude/skills/codebase-index/scripts/cbx.ps1

@@ -0,0 +1,25 @@
+# Windows PowerShell wrapper around the installed `codebase-index` CLI.
+# Mirrors scripts/cbx: whitelists safe subcommands, falls back to `python -m codebase_index`.
+param(
+    [Parameter(Mandatory = $true, Position = 0)]
+    [string]$Subcommand,
+    [Parameter(ValueFromRemainingArguments = $true)]
+    [string[]]$Rest
+)
+
+$ErrorActionPreference = "Stop"
+$allowed = @("search", "explain", "symbol", "refs", "impact", "graph", "stats", "doctor", "update", "index")
+
+if ($allowed -notcontains $Subcommand) {
+    Write-Error "cbx: refusing subcommand '$Subcommand'. Allowed: $($allowed -join ', ')"
+    exit 2
+}
+
+& python -c "import codebase_index" 2>$null
+if ($LASTEXITCODE -eq 0) {
+    & python -m codebase_index $Subcommand @Rest
+    exit $LASTEXITCODE
+}
+$bin = Get-Command codebase-index -ErrorAction SilentlyContinue
+if ($bin) { & $bin.Source $Subcommand @Rest }
+exit $LASTEXITCODE

codebase_index-1.6.0/.claude-plugin/marketplace.json

@@ -0,0 +1,11 @@
+{
+  "name": "codebase-index",
+  "owner": { "name": "codebase-index contributors" },
+  "plugins": [
+    {
+      "name": "codebase-index",
+      "source": "./",
+      "description": "Local-first hybrid codebase index skill with auto-provisioned CLI."
+    }
+  ]
+}

codebase_index-1.6.0/.claude-plugin/plugin.json

@@ -0,0 +1,25 @@
+{
+  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
+  "name": "codebase-index",
+  "displayName": "Codebase Index",
+  "description": "Local-first hybrid codebase index. Auto-provisions its Python CLI on first session start; the skill searches the index so Claude reads only the most relevant files.",
+  "version": "1.6.0",
+  "author": {
+    "name": "codebase-index contributors"
+  },
+  "repository": "https://github.com/denfry/codebase-index",
+  "license": "MIT",
+  "keywords": [
+    "claude-code",
+    "code-search",
+    "semantic-code-search",
+    "codebase-index",
+    "mcp",
+    "ai-agents",
+    "local-first",
+    "tree-sitter",
+    "rag",
+    "sqlite",
+    "fts5"
+  ]
+}

codebase_index-1.6.0/.codex/skills/codebase-index/.skill_version

@@ -0,0 +1 @@
+1.6.0

codebase_index-1.6.0/.codex/skills/codebase-index/SKILL.md

@@ -0,0 +1,198 @@
+---
+name: codebase-index
+description: Use this skill before answering questions about a repository's architecture, implementation locations, symbols, references, dependencies, refactoring impact, data flow, bugs, or where something is implemented. It searches a local hybrid codebase index so Claude reads only the most relevant files instead of scanning the entire project.
+allowed-tools: Bash(python -m codebase_index *), Bash(python3 -m codebase_index *), Bash(codebase-index *), Bash(cbx *), Read, Grep, Glob
+---
+
+# Codebase Index
+
+Use this skill first for codebase questions.
+
+Never scan the entire repository before searching the index.
+
+## When to use
+
+Invoke this skill **before reading any files** when the user asks about this project's code:
+
+- "where is X implemented" / "find X" / "locate the X function"
+- "how does X work" / "explain the X flow"
+- "what breaks if I change X" / "what depends on X" (impact analysis)
+- "who calls X" / "references to X"
+- "trace the data flow of X"
+- "why is this error happening" (error/stack trace)
+- "explain the architecture" / "give me an overview"
+- Any question about symbols, files, dependencies, or refactoring scope
+
+Do **not** use it for: editing files, running the application, or non-code questions.
+
+## How to call the CLI
+
+Use the `codebase-index` CLI directly, or the bundled `cbx` wrapper:
+
+```bash
+codebase-index search "$QUERY" --json
+```
+
+Pick the subcommand by intent:
+
+| User intent | Command |
+|---|---|
+| "how does X work" / "explain X" / "walk me through" | `codebase-index explain "$QUERY" --json` |
+| overview / architecture / "map the codebase" | `codebase-index architecture --json` |
+| general / unsure | `codebase-index search "$QUERY" --json` |
+| keyword / "where is" | `codebase-index search "$QUERY" --json` |
+| a specific symbol name | `codebase-index symbol "<name>" --json` |
+| "who calls / references" | `codebase-index refs "<name>" --json` |
+| "what breaks if I change" | `codebase-index impact "<file-or-symbol>" --json` |
+| "how is X connected to Y" / dependency path | `codebase-index path "<A>" "<B>" --json` |
+| "what is X" / describe a symbol's role | `codebase-index describe "<name>" --json` |
+| visual graph / "open graph" (for the human, not for you to read) | `codebase-index graph "<file-or-symbol>" --open` |
+
+`architecture` returns the codebase map computed at index time — detected modules
+(communities), god nodes (most-connected symbols), surprising cross-module links,
+and suggested questions. Reach for it on "give me an overview" / "where do I
+start" questions instead of a broad `explain`.
+
+`path "A" "B"` returns the shortest dependency/call chain between two symbols or
+files; `describe "X"` returns a node card (definition, callers, callees,
+in/out degree, module, god-node rank). Both annotate edges with a `confidence`
+(`extracted` exact, `inferred` heuristic, `ambiguous` unresolved) — treat a path
+or callee list that leans on `inferred`/`ambiguous` edges as less certain.
+
+The `graph` command renders an HTML dependency graph for a person to look at —
+it is not a retrieval packet. Use it only when the user explicitly wants a visual
+graph; for "what depends on X" answer from `impact`/`refs` instead. In a headless
+session prefer `--output <path>` over `--open`. `--format graphml|dot|neo4j`
+exports the graph for external tools (Gephi/yEd, Graphviz, Neo4j) instead of HTML.
+
+`explain` has a higher default token budget (2200) and HOW_IT_WORKS intent weights — use it whenever the question is about understanding behavior or flow.
+
+For `search`, pick a `--mode` when the intent is clear:
+- `--mode symbol` — pure symbol lookups (faster, no FTS noise)
+- `--mode fts` — text/keyword queries where symbol names don't matter
+- `--mode hybrid` — default; best for mixed queries
+- `--mode vector` — semantic / near-synonym queries ("where do we rate-limit
+  requests" without the exact words). Requires opt-in embeddings; falls back with
+  a clear message when they are not enabled. `hybrid` already blends vectors in
+  when embeddings are on, so reach for `vector` only for pure-semantic recall.
+
+Natural-language kind words such as `method`, `function`, `class`, `interface`,
+`enum`, and `type` constrain the symbol retriever inside `search`.
+
+Use `--json` for programmatic parsing; omit for human-readable output.
+Search/read commands auto-build the index when it is missing; still check
+freshness and run `update`/`index` when responses report stale data.
+
+## Step-by-step workflow
+
+1. **Query the index** using the appropriate subcommand for `$QUERY`.
+2. **Check index freshness** in the response:
+   - `index.exists: false` → run `codebase-index index` first, then re-query.
+   - `index.stale: true`, `files_changed_since_build < 20` → run `codebase-index update`, then re-query.
+   - `index.stale: true`, `files_changed_since_build ≥ 20` → run `codebase-index index` (full rebuild).
+   - Otherwise proceed with results.
+3. **Read ONLY the `recommended_reads`** — use the Read tool with `offset`/`limit` to read the exact line ranges returned. Do not open whole files.
+4. **Answer** with file:line citations (e.g., `src/auth/token.py:88-134`).
+5. **Fallback** only if confidence is low or results are empty (see below).
+
+## Token-budgeted output interpretation
+
+The index returns a **ranked retrieval packet** with:
+
+- `rank` — result position (start with 1-3)
+- `path` — file path
+- `line_start` / `line_end` — exact line range to read
+- `symbols` — symbols found in this range
+- `score` — relevance score
+- `reason` — why this result ranked (e.g., "exact symbol match, 4 callers")
+- `snippet` — compact code excerpt (may already answer the question); `null` means budget was spent — read via `recommended_reads` instead
+- `skeletonized` — when `true`, the `snippet` is a **focus skeleton**: import/signature/class lines and the line(s) matching your query are kept, while function bodies collapse to a marker like `... 24 lines elided (read 88-134)`. Read that line range (or the result's `line_start`/`line_end`) when you need a full body.
+- `elided_lines` — how many source lines the skeleton folded away (`0` when not skeletonized).
+
+Top-level fields:
+
+- `recommended_reads` — the precise `{path, line_start, line_end}` list to open next. This is your read plan.
+- `confidence` — `high` (answer directly), `medium` (read + optionally confirm with one Grep), `low` (use fallback).
+- `fallback_suggestions` — ripgrep patterns and paths to try if the index is weak.
+- `intent` / `mode` — how the query was classified and which retrievers ran;
+  useful to sanity-check a weak result (e.g. a "how does X work" question that
+  resolved to a bare symbol lookup may need `explain` instead).
+- `pagination` — present only when more results exist than fit the page. It
+  reports `has_more` and `next_offset`. To page, re-run `search` with
+  `--offset <next_offset>` (e.g. `search "query" --limit 10 --offset 10`). Prefer
+  refining with a more specific subcommand or raising `--token-budget` first —
+  page only when the top results genuinely miss the answer.
+- `coverage` (on `refs`/`impact` only) — graph-completeness signal. Dependency
+  edges (imports/inheritance) are extracted only for fully supported languages.
+  When `coverage.partial` is `true` (the symbol/file is in a Tier-B language such
+  as Lua), an **empty or short `refs`/`impact` result is inconclusive** — it may
+  just be unanalyzed, not absent. Confirm with a Grep before concluding "nothing
+  references this". `coverage.languages` lists the affected languages.
+
+## Token efficiency rules
+
+- Trust the index. Read the **fewest** files needed — start with rank 1-3 only.
+- Read **line ranges**, not whole files. Use `line_start`/`line_end` with Read's `offset`/`limit`.
+- The `snippet` may already answer the question — re-read only if you need more context.
+- Prefer `search`/`symbol`/`refs`/`impact`/`explain` over manual Grep/Glob — those are expensive fallbacks, not step 1.
+- Don't re-run the query with trivially reworded text; refine with a different subcommand instead.
+- For broad questions (`confidence: low`, architecture, data-flow), raise the budget: `--token-budget 3000`.
+- Test files are demoted in ranking by default. Include "test" in the query to surface them.
+- Snippets are skeletonized by default to fit more results in the budget. The matched line is always preserved; pass `--raw` (CLI) or `raw: true` (MCP) on the rare occasion you need full bodies inline instead of reading the cited line range.
+
+## Fallback behavior
+
+Fall back to built-in search **only** when: results are empty, `confidence` is `low`, or the user asks for something the index clearly doesn't cover.
+
+0. If confidence is consistently low across queries, run diagnostics first:
+   ```bash
+   codebase-index stats --json    # per-language file/symbol counts + graph tier
+   codebase-index doctor          # surface config or security issues
+   ```
+   Low symbol counts for a language may mean the index needs a full rebuild: `codebase-index index`.
+   In `stats`, each language carries `graph: full|partial` (and `doctor` reports a
+   `graph_coverage` finding): `partial` (Tier-B) means `refs`/`impact` lack
+   import/inheritance edges for that language — treat empty results there as
+   inconclusive.
+
+1. Use `fallback_suggestions.ripgrep` patterns from the response via Grep.
+2. If still nothing, Glob for likely paths, then Grep within them.
+3. As a last resort, broaden the search — but tell the user the index was weak here (it may need a rebuild: `codebase-index index`).
+
+Never start with a full-repo scan when the index exists and is fresh.
+
+## Examples
+
+```bash
+# "how does the auth flow work?"
+codebase-index explain "auth flow" --json
+
+# "explain the overall architecture" / "where do I start" — modules, god nodes
+codebase-index architecture --json
+
+# "where is auth token refresh implemented?"
+codebase-index search "auth token refresh" --json
+
+# "what breaks if I change the User model?"
+codebase-index impact "User" --json
+
+# "who calls send_email?"
+codebase-index refs "send_email" --json
+
+# "find the AuthService class"
+codebase-index symbol "AuthService" --json
+
+# precise symbol search (faster, no FTS noise)
+codebase-index search "AuthService" --mode symbol --json
+
+# "how is the API layer connected to the database?"
+codebase-index path "ApiController" "Database" --json
+
+# "what is the Database class and how is it used?"
+codebase-index describe "Database" --json
+
+# generate and open an HTML graph around a file or symbol
+codebase-index graph "User" --direction both --depth 2 --open
+```
+
+Then Read only the returned line ranges and answer with citations.

codebase_index-1.6.0/.codex/skills/codebase-index/examples/hooks/settings.json

@@ -0,0 +1,16 @@
+{
+  "hooks": {
+    "PostToolUse": [
+      {
+        "matcher": "Edit|Write|MultiEdit",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "codebase-index update --quiet >/dev/null 2>&1 &",
+            "timeout": 5
+          }
+        ]
+      }
+    ]
+  }
+}

codebase_index-1.6.0/.codex/skills/codebase-index/scripts/cbx

@@ -0,0 +1,25 @@
+#!/usr/bin/env bash
+# Thin, safe wrapper around the installed `codebase-index` CLI.
+# - Resolves the binary (prefers one on PATH; falls back to `python -m codebase_index`).
+# - Whitelists subcommands so the skill can never invoke destructive ones (clean/init/watch).
+set -euo pipefail
+
+ALLOWED="search explain symbol refs impact graph stats doctor update index"
+
+sub="${1:-}"
+case " $ALLOWED " in
+  *" ${sub} "*) : ;;
+  *)
+    echo "cbx: refusing subcommand '${sub}'. Allowed: ${ALLOWED}" >&2
+    exit 2
+    ;;
+esac
+
+if python -c "import codebase_index" >/dev/null 2>&1; then
+  exec python -m codebase_index "$@"
+elif command -v codebase-index >/dev/null 2>&1; then
+  exec codebase-index "$@"
+else
+  echo "cbx: codebase_index is not importable and codebase-index is not on PATH" >&2
+  exit 127
+fi

codebase_index-1.6.0/.codex/skills/codebase-index/scripts/cbx.ps1

@@ -0,0 +1,25 @@
+# Windows PowerShell wrapper around the installed `codebase-index` CLI.
+# Mirrors scripts/cbx: whitelists safe subcommands, falls back to `python -m codebase_index`.
+param(
+    [Parameter(Mandatory = $true, Position = 0)]
+    [string]$Subcommand,
+    [Parameter(ValueFromRemainingArguments = $true)]
+    [string[]]$Rest
+)
+
+$ErrorActionPreference = "Stop"
+$allowed = @("search", "explain", "symbol", "refs", "impact", "graph", "stats", "doctor", "update", "index")
+
+if ($allowed -notcontains $Subcommand) {
+    Write-Error "cbx: refusing subcommand '$Subcommand'. Allowed: $($allowed -join ', ')"
+    exit 2
+}
+
+& python -c "import codebase_index" 2>$null
+if ($LASTEXITCODE -eq 0) {
+    & python -m codebase_index $Subcommand @Rest
+    exit $LASTEXITCODE
+}
+$bin = Get-Command codebase-index -ErrorAction SilentlyContinue
+if ($bin) { & $bin.Source $Subcommand @Rest }
+exit $LASTEXITCODE

codebase_index-1.6.0/.editorconfig

@@ -0,0 +1,28 @@
+root = true
+
+[*]
+indent_style = space
+indent_size = 4
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true
+
+[*.md]
+indent_size = 2
+trim_trailing_whitespace = false
+
+[*.{yml,yaml}]
+indent_size = 2
+
+[*.{json,jsonc}]
+indent_size = 2
+
+[*.py]
+indent_size = 4
+
+[*.{sh,ps1}]
+indent_size = 2
+
+[Makefile]
+indent_style = tab

codebase_index-1.6.0/.gitattributes

@@ -0,0 +1,7 @@
+# Скрипты-инсталляторы должны иметь LF, иначе ломаются на macOS/Linux
+# (shebang "#!/usr/bin/env sh\r" недопустим). PowerShell-файлы — тоже LF для единообразия.
+*.sh    text eol=lf
+*.ps1   text eol=lf
+*.py    text eol=lf
+# cbx — POSIX-скрипт без расширения; CRLF в worktree ломает shebang при копировании
+cbx     text eol=lf

codebase_index-1.6.0/.github/FUNDING.yml

@@ -0,0 +1,8 @@
+github:
+  patreon: # placeholder
+  ko_fi: # placeholder
+  tidelift: # placeholder
+  community_bridge: # placeholder
+  liberapay: # placeholder
+  issuehunt: # placeholder
+  custom: # placeholder