bloodhound-scout

npx skills add majiayu000/claude-skill-registry --skill bloodhound-scout-autumnsgrove-groveengine --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

# Bloodhound Scout 🐕 The bloodhound doesn't wander aimlessly. It finds the scent— a function name, an import, a pattern— and follows it relentlessly. Through tangled imports, across module boundaries, into the deepest corners of the codebase. The bloodhound maps what it finds, creating trails others can follow. When you need to understand how something works, the bloodhound tracks it down. ## When to Activate - User asks to "find where X is used" or "understand how Y works" - User says "explore this codebase" or "map this system" - User calls `/bloodhound-scout` or mentions bloodhound/tracking - Joining a new project (learning the territory) - Tracing bugs through multiple files - Finding all instances of a pattern - Understanding dependencies and connections - Preparing to refactor (know the territory first) **Pair with:** `elephant-build` for implementing after exploration, `panther-strike` for fixing found issues --- ## The Hunt ``` SCENT → TRACK → HUNT → REPORT → RETURN ↓ ↓ ↓ ↓ ↓ Pick Up Follow Deep Map the Share Scent Trail Dive Territory Knowledge ``` ### Phase 1: SCENT _The nose twitches. Something's been here..._ Establish what we're tracking: **The Starting Point:** What

PRIMARY — Grove Find (the bloodhound's best tools)
gf --agent search "functionName"   # Pick up the scent across the codebase
gf --agent func "getUserById"      # Track down a function's definition
gf --agent usage "UserProfile"     # Follow every trail this name leaves
gf --agent class "PaymentService"  # Find where a class/component lives
gf --agent impact "src/lib/auth.ts" # What trembles when this file changes?
Git context — orient before tracking
gw context                         # Where are we? Branch, recent changes, state
FALLBACK — when the scent needs a finer grain
grep -r "useState.*user" src/ --include="*.tsx"