体验：all-cli report 空工具集只剩 Markdown 表头
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 0
- Avg merge
- 7d 23h
- Merged PRs (30d)
- 24
Description
体验：all-cli report 空工具集只剩 Markdown 表头，没有 catalog/status 下一步
不重复 #63（current 空表）、#56（catalog 无匹配）。
用户路径
all-cli report --tools过滤后没有命中，或 registry 为空。PrintStatusMarkdown原先仍打印# all-cli status report和空表头| Tool | Category | … |，没有行。- 这份 Markdown 是要贴进 issue/PR 的。空表看不出下一步是
all-cli catalog还是all-cli status。
建议改动
空报告写 No tools in this report.，并给出 `all-cli catalog` / `all-cli status`。不要打印空表。
本地 clone 已按此改了一版（未 push / 未开 PR）。
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 by locating the PrintStatusMarkdown implementation and the report path used by all-cli report --tools. Reproduce an empty filtered result or empty registry, then verify that the output replaces the empty Markdown table with No tools in this report. and points users to all-cli catalog and all-cli status.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 76/100