Grepai Trace Callers

Before you refactor or rename a function, you need to know what's calling it. This skill uses GrepAI's trace callers command to find every place in your codebase that invokes a specific function, showing you the caller name, file location, and code context. It works across Go, TypeScript, Python, Rust, and about a dozen other languages, with both fast regex mode and a more accurate tree-sitter based parser. The JSON output makes it scriptable, which is handy for impact analysis or pre-commit checks. It's straightforward call graph traversal, but having it integrated with GrepAI's semantic search means you can understand what a function does and who uses it without switching tools.

skills.sh installs: 812
GitHub stars: 20
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add yoanbernabeu/grepai-skills --skill grepai-trace-callers --agent claude-code

Installs into .claude/skills of the current project.

Files

GrepAI Trace Callers

This skill covers using grepai trace callers to find all code locations that call a specific function or method.

When to Use This Skill

Finding all usages of a function before refactoring
Understanding function dependencies
Impact analysis before changes
Code navigation and exploration

What is Trace Callers?

grepai trace callers answers: "Who calls this function?"

func Login(user, pass) {...}
        ↑
        │
┌───────┴───────────────────┐
│   Who calls Login()?      │
├───────────────────────────┤
│ • HandleAuth (auth.go:42) │
│ • TestLogin (test.go:15)  │
│ • CLI (main.go:88)        │
└───────────────────────────┘

Basic Usage

grepai trace callers "FunctionName"

Example

grepai trace callers "Login"

Output:

🔍 Callers of "Login"

Found 3 callers:

1. HandleAuth
   File: handlers/auth.go:42
   Context: user.Login(ctx, credentials)

2. TestLoginSuccess
   File: handlers/auth_test.go:15
   Context: result := Login(testUser, testPass)

3. RunCLI
   File: cmd/main.go:88
   Context: err := auth.Login(username, password)