codealive-context-engine
Semantic code search and AI-powered codebase Q&A across indexed repositories. Use when understanding code beyond local files, exploring dependencies, discovering cross-project patterns, planning features, debugging, or onboarding. Queries like "How does X work?", "Show me Y patterns", "How is library Z used?". Provides search (fast, returns file locations and descriptions) and chat-with-codebase (slower, costs more, but returns synthesized answers).
npx skills add majiayu000/claude-skill-registry --skill codealive-context-engine-codealive-ai-codealive-skills --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# CodeAlive Context Engine Semantic code intelligence across your entire code ecosystem — current project, organizational repos, dependencies, and any indexed codebase. ## Authentication All scripts require a CodeAlive API key. If any script fails with "API key not configured", help the user set it up: **Option 1 (recommended):** Run the interactive setup and wait for the user to complete it: ```bash python setup.py ``` **Option 2 (not recommended — key visible in chat history):** If the user pastes their API key directly in chat, save it via: ```bash python setup.py --key THE_KEY ``` Do NOT retry the failed script until setup completes successfully. ## Table of Contents - [Authentication](#authentication) - [Tools Overview](#tools-overview) - [When to Use](#when-to-use) - [Quick Start](#quick-start) - [Tool Reference](#tool-reference) - [Data Sources](#data-sources) - [Configuration](#configuration) ## Tools Overview | Tool | Script | Speed | Cost | Best For | |------|--------|-------|------|----------| | **List Data Sources** | `datasources.py` | Instant | Free | Discovering indexed repos and workspaces | | **Search** | `search.py` | Fast | Low | Finding code locations, descripti
- Authentication
- Table of Contents
- Tools Overview
- When to Use
- Quick Start
- 1. Discover what's indexed
- 2. Search for code (fast, cheap)
- 3. Fetch full content (for external repos)
- 4. Chat with codebase (slower, richer answers)
- Tool Reference
- datasources.py — List Data Sources
- search.py — Semantic Code Search
- fetch.py — Fetch Artifact Content
- chat.py — Chat with Codebase
python setup.py python setup.py --key THE_KEY python scripts/datasources.py python scripts/search.py "JWT token validation" my-backend python scripts/search.py "error handling patterns" workspace:platform-team --mode deep python scripts/search.py "authentication flow" my-repo --description-detail full python scripts/fetch.py "my-org/backend::src/auth.py::AuthService.login()" python scripts/chat.py "Explain the authentication flow" my-backend python scripts/chat.py "What about security considerations?" --continue CONV_ID python scripts/datasources.py # Ready-to-use sources
What does the codealive-context-engine skill do?
Semantic code search and AI-powered codebase Q&A across indexed repositories. Use when understanding code beyond local files, exploring dependencies, discovering cross-project patterns, planning features, debugging, or onboarding. Queries like "How does X work?", "Show me Y patterns", "How is library Z used?". Provides search (fast, returns file locations and descriptions) and chat-with-codebase (slower, costs more, but returns synthesized answers).
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill codealive-context-engine-codealive-ai-codealive-skills --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.