From tabnine
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.
npx claudepluginhub tabnine/skills --plugin tabnineThis skill uses the workspace's default tool permissions.
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.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Automates semantic versioning and release workflow for Claude Code plugins: bumps versions in package.json, marketplace.json, plugin.json; verifies builds; creates git tags, GitHub releases, changelogs.
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.