Iagocavalcante Claude Turbo Search
- 15 repo stars
- Updated July 22, 2026
- iagocavalcante/claude-turbo-search
iagocavalcante-claude-turbo-search is a Claude Code plugin that provides optimized file search and semantic indexing for large codebases.
About
iagocavalcante-claude-turbo-search is a Claude Code plugin that promises optimized file search and semantic indexing for large codebases. developers outgrow naive search the moment a side project accretes packages, generated code, and vendored trees—Claude Code sessions stall while the agent re-reads half the disk. This plugin sits in the agent-tooling lane: it improves how your coding agent discovers symbols, related files, and concepts once line counts and directories explode. Catalogue copy emphasizes claude, codebases, indexing, large, optimized, search, semantic, and turbo, which signals performance-oriented retrieval rather than a checklist or a analytics dashboard. Install it when repo navigation is the bottleneck; it complements backend or security plugins but does not replace tests, review, or architecture docs.
- Optimized file search plus semantic indexing aimed at large codebases in Claude Code
- Single-plugin bundle (iagocavalcante/claude-turbo-search) with turbo and semantic keywords
- Reduces context lost to brute-force ripgrep when modules and services multiply
- Fits monorepos and long-lived products where every feature touches distant folders
- Community catalog listing focused on search performance, not code generation
Iagocavalcante Claude Turbo Search by the numbers
- Data as of Jul 26, 2026 (Skillselion catalog sync)
/plugin install iagocavalcante-claude-turbo-search@iagocavalcante/claude-turbo-searchAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 15 |
|---|---|
| Last updated | July 22, 2026 |
| Repository | iagocavalcante/claude-turbo-search ↗ |
What it does
Register turbo search so Claude Code can semantically index and search large codebases without drowning in slow file walks.
Who is it for?
maintainers of large monorepos or legacy apps who live in Claude Code and need faster, semantic codebase navigation.
Skip if: Greenfield tiny repos where built-in search is enough, or teams that forbid local indexing plugins for compliance reasons.
What you get
After you add turbo search, the agent can index and query the codebase semantically so finding the right file or concept in a large project takes fewer round trips.
- Registered claude-turbo-search plugin in Claude Code
- Semantic index of your codebase for faster agent queries
- Improved large-repo file discovery during build, review, and iterate work
By the numbers
- 1 plugin in the iagocavalcante-claude-turbo-search bundle
- 8 catalog keywords including semantic, indexing, large, and optimized
- Community source repository: iagocavalcante/claude-turbo-search
Recommended Plugins
0oastro Kawai Girl Output StyleTransform Claude's responses into kawaii anime girl style\!3
0xbigboss Claude CodeComprehensive configuration system for Claude Code51
2lab Ai Oh My ClaudeClaude Code plugin for AI-powered iterative development loops.37
45ck Claude Sdlc PluginClaude Code plugin for SDLC workflow automation with Storybook planning hub1
70 10 Claude Code Plugins70-10's Claude Code plugins
Aaronbassett Agent FoundryMy personal plugin marketplace for Claude Code4How it compares
Codebase search and indexing plugin, not a deployment MCP server or a security firewall bundle.
FAQ
Who is Iagocavalcante Claude Turbo Search for?
Developers using Claude Code on large or aging codebases who need faster optimized search and semantic indexing instead of manual path guessing.
When should I use Iagocavalcante Claude Turbo Search?
Use it when navigation and cross-module discovery slow every agent session—typically after your repo crosses monorepo scale or heavy generated output.
How do I add Iagocavalcante Claude Turbo Search to my agent?
Install the iagocavalcante/claude-turbo-search plugin from the Claude Code marketplace and run indexing per the repository README before relying on semantic queries.