一键导入
cocoindex-code-search
Use the pinned external CocoIndex Code MCP workflow for broad repository routing, then prove exact candidates with rg and direct file reads.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use the pinned external CocoIndex Code MCP workflow for broad repository routing, then prove exact candidates with rg and direct file reads.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | cocoindex-code-search |
| description | Use the pinned external CocoIndex Code MCP workflow for broad repository routing, then prove exact candidates with rg and direct file reads. |
| metadata | {"origin":"adapted from ZMB-UZH/omero-docker-extended at b27dbe990703d64d13e540c40cf4e122954c664d"} |
Use this skill only when a broad question would otherwise require a large
repository scan. Exact strings, symbols, filenames, and small result sets go
directly to rg.
cocoindex-code.python tools/cocoindex_agent_search.py mcp-install.python tools/cocoindex_agent_search.py mcp-smoke.
Registration alone is not evidence; the JSON-RPC initialize and tool-list
probes must pass.index --allow-dirty-index for an intentional worktree snapshot, or
search --refresh "<query>" on a clean tree.python tools/cocoindex_agent_search.py search --limit 5 "<query>".rg and direct reads in the live repo.cocoindex-code[full]==0.2.37 pinned.ccc init in the live checkout and never commit
.cocoindex_code/.AGENT_COCOINDEX_HOME or the platform-specific external default..env files, credentials, ignored files, or private
artifacts. Binary files are not semantic-search evidence.The portable contract, package hashes, and benchmark inputs are documented in
docs/AGENT_WORKFLOWS.md and docs/reference/cocoindex-code-agent-benchmark-2026-07-11.md.
Bound repository context reads and semantic-search output without weakening source, test, or evidence verification.
Choose staged contract tests that catch partial AI-generated fixes across models, data, risk, execution ownership, and CLI/Windows parity.
Keep concise user docs and machine-readable model evidence synchronized with real behavior without losing provenance or caveats.
Apply four anti-error coding principles plus this repository's stricter financial-evidence, safety, and single-session rules.
Research the existing implementation, tests, primary technical sources, and financial rationale before adding trading code or dependencies.
Audit financial, data, model, and dependency claims for primary-source quality, dates, provenance, and reproducibility before implementation or publication.