Claude-ast-index-search

This skill should be used when the user asks to "find a class", "search for symbol", "find usages", "find implementations", "search codebase", "find file", "class hierarchy", "find callers", "module dependencies", "unused dependencies", "project map", "project conventions", "project structure", "what frameworks", "what architecture", "find Perl subs", "Perl exports", "find Python class", "Go struct", "Go interface", "find React component", "find TypeScript interface", "find Rust struct", "find Ruby class", "find C# controller", "find Dart class", "find Flutter widget", "find mixin", "find Scala trait", "find case class", "find object", "find PHP class", "find Laravel model", "find PHP trait", or needs fast code search in Android/Kotlin/Java, iOS/Swift/ObjC, Dart/Flutter, TypeScript/JavaScript, Rust, Ruby, C#, Scala, PHP, Perl, Python, Go, C++, or Protocol Buffers projects. Also triggered by mentions of "ast-index" CLI tool.

Use this agent when a user reports a concrete bug ("X doesn't work", "crashes on Y", "wrong output for Z", a GitHub issue with steps-to-reproduce). The agent reproduces the bug, locates the root cause, applies a minimal fix, proves the fix works with a regression test, and confirms nothing else broke. Do NOT use for feature requests, refactors, or open-ended "look at this code" asks — those are different profiles.

Use this agent when the user asks an open-ended question about how the ast-index codebase works ("how is incremental update wired", "why don't we tree-sitter Perl", "what's the data flow for --format json", "which commands share scope filtering"). The agent reads the code, traces connections, and returns a structured answer with file:line citations. It does NOT edit code, does NOT run destructive commands, and does NOT speculate — every claim is grounded in a file you can open.

Use this agent to review a set of changes before they ship — staged/unstaged diff, a specific commit range, a PR description, or "the latest commit". The agent reads the diff against project rules in CLAUDE.md and .claude/rules/*, runs the build and test suite, and reports what's good, what's wrong, and what's missing. It does NOT fix anything itself — the point is feedback, not rework.