메뉴
Use when searching, exploring, or investigating remote repositories using Tabnine's Context Engine. Activates for cross-repo questions, service architecture questions, PR impact analysis, or when verifying usage of external APIs against real codebase examples.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | codebase-search |
| description | Use when searching, exploring, or investigating remote repositories using Tabnine's Context Engine. Activates for cross-repo questions, service architecture questions, PR impact analysis, or when verifying usage of external APIs against real codebase examples. |
When the user asks about remote codebases, always use the tabnine-context MCP tools to search and explore. Do not guess or rely on training data — fetch real information from the indexed repositories.
The tabnine-context MCP server exposes tools for:
Cast a wide net first using semantic search and files search, then narrow down with symbol tools. If the first search doesn't return useful results, try different queries or filters before giving up. Cross-reference multiple repos when investigating service interactions.
Onboard a Context Engine tenant: confirm a model + embedder are configured, connect data sources (GitHub/GitLab/Jira/… repos + credentials) and ingest, then immediately show what CTX understood about each repo (what it is, stack, what it does, what it talks to) with a live semantic-search demo and an invitation to ask questions — and kick off the slower enrichment agents that build the service/dependency graph as a follow-on. Use for "set up / onboard / get started with CTX", "connect repos", or "what does CTX know about my system".
Set up and route Context Engine CLI (ctx-cli) work — install, authenticate, check version, discover tools, and pick the right tool by intent. Start here for anything involving ctx-cli or the Context Engine; it routes to the ctx-onboarding, ctx-search, ctx-security, ctx-guidelines, and ctx-investigate skills.
Apply and audit a team's coding standards with ctx-cli — fetch managed coaching guidelines to write or review code to spec, and inspect discovered AI-guideline files (CLAUDE.md, .cursorrules, AGENTS.md) for coverage and cross-repo drift.
Investigate services and assess change impact with ctx-cli — one-call service investigation (deps, owners, runbooks), blast radius, incident response, dependency/package safety checks, package migration, and business-flow understanding.
Search a team's codebase and knowledge graph with ctx-cli — find where code is implemented (code_search), find entities by natural-language query, and traverse graph relationships between services, libraries, and code. Use to locate source or explore what an entity connects to.
Triage and resolve security findings with ctx-cli — the CVE and SAST resolution inboxes, each row carrying a ready-to-apply fix diff or advisory. Use for any security search or CVE/SAST remediation work.
