体验:catalog 无匹配只报 No tracked tools,不说下一步
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 0
- Avg merge
- 7d 23h
- Merged PRs (30d)
- 24
Description
体验问题:catalog 搜不到工具时没有下一步
Skip: doctor vs diagnose help (#54) and inherited --no-progress (#55). This is a different command.
Current design
all-cli catalog [search] lists the built-in tool catalog without running those tools. A miss prints:
No tracked tools match "not-a-real-tool".
all-cli describe already suggests a nearby ID (did you mean "kubectl"?). Catalog does not. It also does not say how to list the full catalog or how to inspect one tool.
--ids on a miss prints nothing at all. Human mode at least says there was no match, then stops.
Why this is a problem
- First-time users treat
catalogas the discovery surface. A typo or category word that is not a substring looks like an empty product. - The next useful commands already exist:
all-cli catalogwith no query, andall-cli describe <id>. - Agents parsing human output get a dead end instead of a recovery command.
Suggested change
On a human-mode empty search, print the miss, then one recovery line: list the catalog, or did you mean plus all-cli catalog <id> when toolIDSuggestion has a hit. Leave --json and --ids machine shapes unchanged.
Do not change doctor/diagnose help in this pass.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the all-cli catalog command and compare its human-mode miss path with all-cli describe's suggestion behavior. Check the no-query catalog output and toolIDSuggestion handling; done means human empty searches show a recovery line while --json and --ids remain unchanged, with doctor/diagnose help unaffected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100