grepai-languages

Lists GrepAI supported languages and configures indexing and call-graph tracing per language.

Updated May 12, 2026

Search Tags:#semantic search #configuration #language support #call graph #code indexing #grepai #call tracing

Ready to run

npx skills add https://github.com/eduardtomasek/codex-dev-stack --skill grepai-languages-eduardtomasek

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: grepai-languages
Source: https://github.com/eduardtomasek/codex-dev-stack/tree/main/skills/.agents/grepai-languages
Command: npx skills add https://github.com/eduardtomasek/codex-dev-stack --skill grepai-languages-eduardtomasek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When setting up GrepAI for semantic code search and call tracing, it is unclear which programming languages support full call-graph tracing versus index-only search, and how to configure language-specific settings correctly. ## Core Features & Use Cases - Language Support Matrix: Shows which languages get full index plus trace support (Go, TypeScript, Python, Rust, C/C++, Java, and more) versus index-only support (Ruby, Swift, Kotlin, and others). - Trace Configuration: Provides ready-to-use YAML snippets for enabling languages, excluding test files, and choosing fast or precise trace modes. - Use Case: You are onboarding a multi-language repository with a Go backend and TypeScript frontend. Use this Skill to confirm both languages support tracing, then generate a config that enables `.go`, `.ts`, and `.tsx` while excluding test files. ## Quick Start Ask which languages GrepAI can trace and generate a trace configuration for my Go and TypeScript project excluding test files.

Frequently Asked Questions about grepai-languages

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

FAQPage Schema

Which languages does GrepAI support for call tracing?▼

GrepAI supports full call tracing for Go, JavaScript, TypeScript, Python, PHP, C, C++, Rust, Zig, C#, Java, and Pascal. Languages like Ruby, Swift, Kotlin, and Scala are indexed for semantic search but have no trace support.

How do I configure GrepAI trace for specific languages?▼

Add the desired extensions under trace.enabled_languages in .grepai/config.yaml, such as .go, .ts, and .py. Use exclude_patterns to skip test files like *_test.go or *.spec.ts for cleaner trace results.

Does GrepAI work with multi-language projects?▼

Yes, GrepAI handles multi-language repositories by listing all needed extensions in enabled_languages, for example .go for a backend and .ts and .tsx for a frontend. Index-only files like SQL can still be searched semantically.

Why is GrepAI trace missing for my language?▼

Trace is missing when the language extension is not listed in enabled_languages or the language only has index support. GrepAI detects languages by file extension only, not shebangs or content analysis.

What is the difference between GrepAI index and trace?▼

Index chunks and embeds any text file for semantic search without language-specific parsing. Trace requires language-specific parsing to extract function definitions and calls, building caller and callee relationships in fast or precise mode.