This skill should be used when code search, file/directory summary lookup, or concept-guide lookup is needed (whether explicitly requested or as part of completing a task), when indexing the codebase after changes, or when the user asks about ccc, cocoindex-code, or the codebase index. Trigger phrases include 'search the codebase', 'find code related to', 'describe this file', 'read the concept guide', 'update the index', 'ccc', 'cocoindex-code'.
The ccc skill provides semantic code search and index management capabilities for a project codebase through the CocoIndex Code CLI. It is designed to help users quickly locate code related to concepts, behaviors, features, or architectural patterns without relying on exact syntax matching. Instead of searching for literal strings, users can search by intent or functionality, such as authentication flows, retry logic, or database pooling. The skill also manages project initialization and indexing automatically, ensuring the codebase remains searchable and up to date without requiring manual setup steps from the user.
A core capability of the skill is semantic searching across indexed project content, including source files, summaries, and curated concept guides. It supports filtering search results by programming language and file path, making it easier to narrow searches within large repositories. The skill also supports pagination for retrieving additional results and provides workflows for exploring matching files and line ranges in more detail. In addition to code search, the skill can surface synthesized file and directory summaries as well as curated guides when they are relevant to the query. The indexing lifecycle is handled automatically, including project initialization, index refreshes after significant code changes, and retry logic when initialization errors occur.
This skill is intended for developers, technical agents, and engineering workflows that require efficient navigation and understanding of large codebases. Common use cases include investigating implementation details, locating related functionality, understanding project structure, reviewing summaries of files or directories, and maintaining a searchable semantic index after refactors or file additions. It is especially useful in projects where traditional text-based search is insufficient for discovering conceptually related code.
Use the command `ccc search <query terms>` and describe the functionality or concept you want to find, such as authentication logic or retry handling.
Yes. Searches can be filtered using `--lang` for programming languages and `--path` for glob-based path filtering relative to the project root.
If initialization errors occur, the workflow runs `ccc init` followed by `ccc index` before retrying the original command.
Yes. The index should be refreshed after significant code changes such as refactors, renamed modules, or new files to keep search results accurate.
Yes. Search results may include file or directory summaries and curated concept guides, which can be accessed using `ccc describe <path>` or `ccc guide <slug>` when provided in search output.
Quick Setup:
.claude/skills/Repository
cocoindex-io/cocoindex-code