langfuse-codebase-navigator

Routes tasks to the correct Langfuse repository, code area, and agent skill.

34.0k|3.7k|Updated May 18, 2023
One-click install
npx skills add https://github.com/langfuse/langfuse --skill langfuse-codebase-navigator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: langfuse-codebase-navigator
Source: https://github.com/langfuse/langfuse/tree/main/.agents/skills/langfuse-codebase-navigator
Command: npx skills add https://github.com/langfuse/langfuse --skill langfuse-codebase-navigator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Working across the Langfuse organization means choosing among dozens of public and private repositories, monorepo code areas, and repo-local agent skills; picking the wrong one wastes effort and risks editing the wrong codebase.

Core Features & Use Cases

  • Repository Routing: Classifies requests by domain (product app, docs, SDKs, deployment, cloud infrastructure, agent skills) and maps them to the correct Langfuse repository.
  • Skill Selection: Points to the most specific repo-local skill under .agents/skills before deeper implementation, debugging, or review work.
  • Search Recipes: Provides concrete rg and gh command patterns for local sibling checkouts and GitHub org-wide fallback search.
  • Use Case: When asked to fix a trace ingestion bug, the skill routes you to langfuse/langfuse, opens worker/src/services and packages/shared/src/server, and suggests loading the backend-dev-guidelines skill before editing.

Quick Start

Ask the agent to use the langfuse-codebase-navigator skill to determine which Langfuse repository, folders, and skills apply to your task before starting work.

Frequently Asked Questions about langfuse-codebase-navigator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the right Langfuse repository for a task?

Classify the request by domain first: product app and API work goes to langfuse/langfuse, documentation to langfuse-docs, SDK behavior to langfuse-js or langfuse-python, and deployment to langfuse-k8s or the Terraform module repos. The repository-map reference lists every repo with its routing conditions.

How do I search code across the Langfuse GitHub organization?

Search local sibling checkouts first with ripgrep, for example rg -n "symbolName" web/src packages/shared/src worker/src in the main repo. Fall back to gh search code "query org:langfuse" only for repos not cloned locally or to confirm the current default branch.

Which agent skill should I use for Langfuse backend work?

For backend work in langfuse/langfuse, load the backend-dev-guidelines skill covering tRPC, API endpoints, worker processors, Prisma, and ClickHouse services. Frontend changes under web/ should also check frontend-browser-review and the Vercel React skills.

Does the navigator work without all Langfuse repos cloned locally?

Yes, but local clones are preferred for search speed and accuracy. If a needed repo is missing, clone it into the same parent directory with gh repo clone langfuse/<repo>, or use GitHub code search as a fallback.

When should I ask a clarifying question instead of routing automatically?

Ask one concise clarifying question when multiple routes are plausible and acting in the wrong repository would be risky, such as tasks spanning private sparse-metadata repos. Otherwise choose the most likely route and proceed.