t1k:scout

Field	Value
Module	`t1k-base`
Version	`2.17.3`
Effort	`low`
Tools	`Agent`, `Bash`, `Glob`, `Grep`, `Read`, `Task`

Keywords: codebase, explore, find, grep, navigate, search, usages

How to invoke

/t1k:scout
[query]

TheOneKit Scout — Codebase Exploration

Context-aware codebase search using the Explore agent with skill context injection.

Skill Activation

Read ALL kit-level .claude/t1k-activation-*.json files PLUS module-level fragments under .claude/modules/<module>/ matching the same glob. Match query keywords against ALL fragments. Activate all matching skills before exploring.

When resolving a mappings[].skills[] entry to a skill dir, accept BOTH the bare-slug form (nakama-rpc) and the full-prefixed form (t1k-nakama-rpc) — the CI prefixer self-heals legacy bare refs at release time but the SSOT in fragment files stays bare. Refs that don’t resolve via either form are drift; surface to the user (consult t1k-doctor check #47).

Module-Aware Search (if `installedModules` or `modules` present in metadata.json)

Follow protocol: skills/t1k-modules/references/module-detection-protocol.md

Read .claude/metadata.json → installed modules
Annotate each finding with its module: “Found in module: dots-core” or “Found in: kit-wide”
If searching for a pattern, prioritize skills from the relevant module
Include module ownership in result labels

Default Search Paths

Read .t1k-manifest.json to determine installed kit paths, then search:

Path	What it Contains
Source code root	Project implementation files
`.claude/skills/`	Encoded knowledge base
`docs/`	Technical documentation

Process

Activate skills — match query keywords via activation fragments
Scope query — map keywords to relevant source paths
Run Explore agent with scoped paths + query
Annotate results — label each finding as Source / Skill / Doc
Reuse check — if query is about implementing something, flag existing code first

Cross-Repo Search (—cross-repo flag)

/t1k:scout --cross-repo <query>

Requires: gh CLI authenticated. Default scope is current project only.

Read .claude/metadata.json → installedModules → collect unique repository values
For each repo: gh search code --repo {owner}/{repo} "{query}" --json path,repository,textMatches

Results format per match:

[{repo}] {file-path}
> {match context — 3 lines around match}

Rank: exact match > partial match. Cap at 10 results per repo.
If gh unavailable: warn and fall back to local search only

Agent

Uses Explore subagent — built-in, no registry delegation needed.

Scope

Codebase exploration only — does NOT implement, modify, or plan.