By name: ck-get-keyword-map description: Build a seed-to-related keyword map from indexed results. Use when file-first retrieval is weak/noisy and you need fallback folder scoping with ck find-files.
ck get-keyword-map — Query Precision Helper
Use this for the fallback scope path, not as the default first step.
Default discovery is ck find-files; run ck get-keyword-map when you need to pivot to ck find-files.
Syntax
.claude/skills/ck/ck get-keyword-map --query "<multi-keyword description>" [--must "<provider>"] [--top <n>] [--per-keyword <n>]
Options
| Option | Default | Description |
|---|---|---|
--query <text> |
required | Multi-keyword description of the area you need |
--must <text> |
off | Required provider/concept focus (repeatable) |
--top <n> |
12 | Number of top semantic folders analyzed |
--per-keyword <n> |
50 | Related terms returned per seed keyword (adaptive: may return fewer when quality drops) |
--repo <path> |
auto | Repo root |
--verbose |
off | Prints index build/refresh progress |
Query Wording (Important)
- Use lexical query terms that likely exist in indexed code metadata: path/folder words, file-name words, type names, and method/member words.
- Avoid natural-language questions; this command works best with concrete code-like tokens.
- Use 3-7 high-signal terms (domain + workflow + operation/symbol).
Good:
adyen terminal card-present refundinventory reservation allocate async
Weak:
where is refund logichow does this feature work
Output shape
matched-query-keywords: query terms that were found in top foldersunmatched-query-keywords: query terms not found in top foldersglobal-keyword-hints: top hints from the current result scopekeyword-map: per-seed related terms (seed: t1, t2, ...)
Usage pattern
- Run
ck find-files --query "..." --task "..."first - If file-first results are weak/noisy, run
ck get-keyword-map --query "..." - Then run
ck find-files --query "..." --task "..."using precision terms from step 2 - Folders from
find-filesare source of truth for fallback exploration