> For the complete documentation index, see [llms.txt](https://code-visualization.shawnxie.top/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://code-visualization.shawnxie.top/shi-jian-pian/case-intro.md).

# 业界实践

汇总了“代码可视化”在业界的实践案例，提供更多的应用灵感。目前调研到大致有以下使用场景（各场景之间可能存在功能交叉）：

* 代码理解与分析
* 代码质量检测
* 代码性能分析
* 精准测试
* 代码自动重构
* 架构治理

等等...

#### 可视化工具收集

* [12 Best Code Visualization Tools Reviewed For 2024](https://thectoclub.com/tools/best-code-visualization-tools/)
* [What are the best code visualization and analysis tools?](https://www.slant.co/topics/16888/~code-visualization-and-analysis-tools)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://code-visualization.shawnxie.top/shi-jian-pian/case-intro.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.