体验：all-cli report 空工具集只剩 Markdown 表头

Open Beginner friendly
#65 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
go
Domain
cli

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.

Description

体验：all-cli report 空工具集只剩 Markdown 表头，没有 catalog/status 下一步

不重复 #63（current 空表）、#56（catalog 无匹配）。

用户路径
  1. all-cli report --tools 过滤后没有命中，或 registry 为空。
  2. PrintStatusMarkdown 原先仍打印 # all-cli status report 和空表头 | Tool | Category | … |，没有行。
  3. 这份 Markdown 是要贴进 issue/PR 的。空表看不出下一步是 all-cli catalog 还是 all-cli status。
建议改动

空报告写 No tools in this report.，并给出 `all-cli catalog` / `all-cli status`。不要打印空表。

本地 clone 已按此改了一版（未 push / 未开 PR）。

Dominant language
Go
Stars
1
Forks
0
Avg merge
7d 23h
Merged PRs (30d)
24

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from oldwinter/all-cli

All issues in oldwinter/all-cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.