Gograph Go Repository Intelligence
ozgurcd/gograph
Gives an agent working in a Go codebase a structural view through a local MCP server: call graphs, blast-radius and impact analysis, and bounded first-call exploration.
Semantic code search and call-graph tracing. An agent skill from yoanbernabeu/grepai.
Install Grepai
$ npx skills add yoanbernabeu/grepai --skill grepai -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install yoanbernabeu/grepai grepai --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/yoanbernabeu/grepai.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/grepai .claude/skills/grepai && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "grepai" agent skill from https://github.com/yoanbernabeu/grepai/tree/main/.claude/skills/grepai into .claude/skills/grepai/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grepai", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/yoanbernabeu/grepai/tree/main/.claude/skills/grepaiType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add yoanbernabeu/grepai --skill grepai -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install yoanbernabeu/grepai grepai --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yoanbernabeu/grepai.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/grepai .agents/skills/grepai && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "grepai" agent skill from https://github.com/yoanbernabeu/grepai/tree/main/.claude/skills/grepai into .agents/skills/grepai/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grepai", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add yoanbernabeu/grepai --skill grepai -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install yoanbernabeu/grepai grepai --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yoanbernabeu/grepai.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/grepai .cursor/skills/grepai && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "grepai" agent skill from https://github.com/yoanbernabeu/grepai/tree/main/.claude/skills/grepai into .cursor/skills/grepai/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grepai", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/yoanbernabeu/grepai.git --path .claude/skills/grepai--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add yoanbernabeu/grepai --skill grepai -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install yoanbernabeu/grepai grepai --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yoanbernabeu/grepai.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/grepai .gemini/skills/grepai && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "grepai" agent skill from https://github.com/yoanbernabeu/grepai/tree/main/.claude/skills/grepai into .gemini/skills/grepai/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grepai", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install yoanbernabeu/grepai grepaiInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add yoanbernabeu/grepai --skill grepai -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/yoanbernabeu/grepai.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/grepai .github/skills/grepai && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "grepai" agent skill from https://github.com/yoanbernabeu/grepai/tree/main/.claude/skills/grepai into .github/skills/grepai/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grepai", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add yoanbernabeu/grepai --skill grepai -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install yoanbernabeu/grepai grepai --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yoanbernabeu/grepai.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/grepai .opencode/skills/grepai && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "grepai" agent skill from https://github.com/yoanbernabeu/grepai/tree/main/.claude/skills/grepai into .opencode/skills/grepai/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grepai", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
grepai- GitHub stars
- 1.9k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 380 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
Semantic code search and call-graph tracing. An agent skill from yoanbernabeu/grepai.
- Works in 4 steps: Start with grepai search for ranked… → Add git grep -ilE '' for the exhaustive… → Use grepai trace to understand function… → …
- Intent questions (where is authentication handled?)
- SKILL.md covers grepai: ranked semantic search…, Tool Choice, Recall-Safe Combo (cheap AND… and How to Use This Skill, plus 3 more sections
- Calls git
What it does
Grepai is an agent skill from yoanbernabeu/grepai. Semantic code search and call-graph tracing. Use for intent questions ('where is authentication handled?'), exploring unfamiliar code, or tracing callers/callees — as a ranking layer on top of exact-match Grep, not a replacement for it.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Codebase onboarding. It works with Model Context Protocol and Go. The repository describes itself as: Semantic Search & Call Graphs for AI Agents (100% Local). The licence is MIT.
When your agent uses it
- Intent questions (where is authentication handled?)
- Exploring unfamiliar code
- Tracing callers/callees — as a ranking layer on top of exact-match Grep
- Not a replacement for it
Example prompts
- “where is authentication handled?”
- “/grepai”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Start with grepai search for ranked starting points
- Add git grep -ilE '' for the exhaustive file checklist (names only)
- Use grepai trace to understand function relationships
- Use Read on ranked hits first, then on relevant checklist files grepai did not rank
What it can do on your machine
Read from SKILL.md and the folder at commit eb941fe. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Grepai loads about 1.1k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 380 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from yoanbernabeu/grepai at commit eb941fe, republished under its MIT licence (© yoanbernabeu). 380 words, ~1,055 tokens.
Download SKILL.mdSave it as
.claude/skills/grepai/SKILL.md (or your agent's skills folder).- name
- grepai
- description
- Semantic code search and call-graph tracing. Use for intent questions ('where is authentication handled?'), exploring unfamiliar code, or tracing callers/callees — as a ranking layer on top of exact-match Grep, not a replacement for it.
grepai: ranked semantic search (not a Grep replacement)
grepai search answers a natural-language query with ~10 scored chunks in one
call — a ranked starting point at a fraction of the tokens of dumping raw grep
output (--json --compact alone saves ~80%). It is a ranking layer, not an
exhaustive one: a vector top-10 can miss a relevant file that keyword grep
finds trivially. The rules below save tokens without losing recall.
Tool Choice
| Query | Tool |
|---|---|
| Exact identifiers, imports, string literals | built-in Grep / git grep — fastest, exhaustive |
Intent with a canonical syntax anchor (@main, func main(, class AppDelegate) | Grep the anchor — many "intent" questions are exact-match queries in disguise |
| Intent with no obvious anchor ("where are errors handled?") | recall-safe combo below |
| Function relationships (callers/callees) | grepai trace — grep has no equivalent |
File patterns (**/*.go) | Glob |
Recall-Safe Combo (cheap AND exhaustive)
grep's token cost is in dumping content lines; its recall is nearly free when you ask for file names only. For an intent query, run both cheap layers:
# 1. Ranking: ~10 scored chunks, one call
grepai search "where errors are handled and logged" --json --compact
# 2. Recall: exhaustive candidate checklist — file NAMES only, ~zero tokens
git grep -ilE 'error|handl|logg' | head -50Read grepai's top hits first, then scan the checklist for relevant-looking files grepai did not rank — read those too. Never dump full grep content output for an intent query; the file list gives you grep's recall at ~1% of the tokens.
If grepai's top hits are docs/reports instead of code: scope with
grepai search "<query>" --path <srcdir>, or add generated content to a
.grepaiignore.
Show full SKILL.md (150 more words)Show less
How to Use This Skill
Semantic Search
Use grepai search to find code by describing what it does:
# Search with natural language (ALWAYS use English for best results)
grepai search "user authentication flow"
grepai search "error handling middleware"
grepai search "database connection pooling"
grepai search "API request validation"
# JSON output for AI agents (--compact saves ~80% tokens)
grepai search "authentication flow" --json --compact
# Limit results
grepai search "error handling" -n 5Call Graph Tracing
Use grepai trace to understand function relationships:
# Find all functions that CALL a symbol
grepai trace callers "HandleRequest" --json
# Find all functions CALLED BY a symbol
grepai trace callees "ProcessOrder" --json
# Build complete call graph (both directions)
grepai trace graph "ValidateToken" --depth 3 --jsonQuery Best Practices
Do:
grepai search "How are file chunks created and stored?"
grepai search "Vector embedding generation process"
grepai search "Configuration loading and validation"
grepai trace callers "Search" --jsonDon't:
grepai search "func" # Too vague
grepai search "error" # Too generic
grepai search "HandleRequest" # Use Grep for exact matchesRecommended Workflow
- Start with
grepai searchfor ranked starting points - Add
git grep -ilE '<keywords>'for the exhaustive file checklist (names only) - Use
grepai traceto understand function relationships - Use
Readon ranked hits first, then on relevant checklist files grepai did not rank
Fallback
If grepai fails (not running, index unavailable, or errors), fall back to standard Grep/Glob tools. Common issues:
- Index not built: Run
grepai watchto build/update the index - Embedder not available: Check that Ollama is running or OpenAI API key is set
Keywords
semantic search, code search, natural language search, find code, explore codebase, call graph, callers, callees, function relationships, code understanding, intent search, code exploration, recall, token savings
© yoanbernabeu, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/grepai of yoanbernabeu/grepai.
Open the folder on GitHubat commit eb941fe
Compare with similar skills
Grepai next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Grepai this skillyoanbernabeu/grepai | 1.9k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Gograph Go Repository Intelligenceozgurcd/gograph | 227 | — | ~4.8k | Automated safety check: Notes | MIT | |
| Golang Goplscontext-labs/whip | 1.1k | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Symdex Code Searchhusnainpk/SymDex | 208 | — | ~2.3k | Automated safety check: Pass | MIT | |
| GitDiagram Repository Overviewahmedkhaleel2004/gitdiagram | 18k | — | ~427 | Automated safety check: Pass | MIT | |
| Explore Codebase with Graphtirth8205/code-review-graph | 32k | 1 repos | ~335 | Automated safety check: Pass | MIT |
Similar skills
Golang Gopls
context-labs/whip
Golang semantic code intelligence via gopls — go-to-definition, references, call hierarchy, symbols, diagnostics, rename, refactors.
Symdex Code Search
husnainpk/SymDex
This skill should be used when finding, tracing, or understanding code in a repository with SymDex available.
GitDiagram Repository Overview
ahmedkhaleel2004/gitdiagram
Explains the architecture of a public GitHub repository through GitDiagram: how the code is organized, the main components with paths, and a Mermaid diagram.
Explore Codebase with Graph
tirth8205/code-review-graph
Navigates a codebase through the code-review-graph MCP tools: architecture overview, symbol search, caller and callee tracing, flows and oversized functions.
- Official
Context Handling in fp-go
IBM/fp-go
Covers handling Go's context.Context idiomatically in fp-go code: reading and scoping context through operators, timeouts, cancellation and converting ctx-first functions.
More from yoanbernabeu/grepai
Release
yoanbernabeu/grepai
Create a new release for grepai. An agent skill from yoanbernabeu/grepai.
Related
Works with
Categories
Questions about Grepai
What does Grepai do?
Semantic code search and call-graph tracing. An agent skill from yoanbernabeu/grepai. Grepai is an agent skill from yoanbernabeu/grepai. Semantic code search and call-graph tracing.
When should I use Grepai?
Grepai fits situations like: intent questions (where is authentication handled?); exploring unfamiliar code; tracing callers/callees — as a ranking layer on top of exact-match Grep; not a replacement for it.
How do I install Grepai in Claude Code?
Run `npx skills add yoanbernabeu/grepai --skill grepai -a claude-code`. Or copy the skill folder (.claude/skills/grepai in yoanbernabeu/grepai) into .claude/skills/grepai in your project. Claude Code loads it when a task matches its description.
How do I install Grepai in Codex?
Run `npx skills add yoanbernabeu/grepai --skill grepai -a codex`. Or copy the skill folder (.claude/skills/grepai in yoanbernabeu/grepai) into .agents/skills/grepai in your project. Codex loads it when a task matches its description.
Can I use Grepai in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yoanbernabeu/grepai --skill grepai -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/grepai, .gemini/skills/grepai, .github/skills/grepai and .opencode/skills/grepai in your project.
What does Grepai need to run?
Going by SKILL.md and its folder, Grepai needs the command-line tools its instructions call (git).
Does Grepai access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Grepai safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Grepai use?
Grepai is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Grepai use?
About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Grepai?
Skills that share tags, products or a category with Grepai: Gograph Go Repository Intelligence (ozgurcd/gograph, 227 stars), Golang Gopls (context-labs/whip, 1.1k stars), Symdex Code Search (husnainpk/SymDex, 208 stars) and GitDiagram Repository Overview (ahmedkhaleel2004/gitdiagram, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Grepai?
yoanbernabeu (a GitHub user) maintains it in yoanbernabeu/grepai, which has 1,901 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 21, 2026.
Source: yoanbernabeu/grepai on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.