Loading...
Loading...
Found 8 Skills
Reference for all GrepAI MCP tools. Use this skill to understand available MCP tools and their parameters.
Investigate suspected bugs with git archaeology and root cause analysis. Triggers: "bug", "broken", "doesn't work", "failing", "investigate bug".
Use when hunting a regression across many commits or tracing the origin of a line/function/string — covers automated bisect, skip, replay, blame -L/-C/-w, and pickaxe search (-S/-G)
Supported programming languages in GrepAI. Use this skill to understand which languages can be indexed and traced.
Interactive code execution path tracer that explains how code flows from entry point to output. Uses step-by-step navigation with AskUserQuestion to explore conditional branches and function calls. Use when: - User asks "How does X work in this codebase?" - User wants to understand HTTP request/response flow - User asks about middleware execution order - User wants to trace a function call chain - User asks "What happens when..." questions - User wants to learn how code paths connect Keywords: trace, flow, execution, path, call chain, middleware, request handling, what happens, how does, step through, follow the code
Trace and explain how an existing code path or subsystem works.
Deep multi-agent investigation of the current local codebase. Use when Codex needs an evidence-backed understanding of repository architecture, a subsystem, a code path, package or module boundaries, build or runtime wiring, change impact, or competing implementations inside the repo before making edits. Trigger on requests like "research this codebase", "how does this repo work", "trace feature X", "explain this architecture", "map this subsystem", or "what files are involved in this behavior".
Explain how a feature, pipeline, workflow, or concept in this codebase actually works.