> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/documentation/zh/collaborate/comments.md).

# 评论

向团队提问，或接收你创建内容的反馈

评论可让你针对特定内容提供反馈——而无需离开 GitBook 的上下文。

### 添加评论 <a href="#comment-within-your-content" id="comment-within-your-content"></a>

你可以点击 **评论** 按钮 <picture><source srcset="broken://files/pDeFaKnBm2RYQrk7saJ9" media="(prefers-color-scheme: dark)"><img src="https://2111890564-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNkEGS7hzeqa35sMXQZ4X%2Fuploads%2Fgit-blob-244524032b40cae991b97359a93b026fee379b9e%2F25_01_10_comment_icon_light.svg?alt=media" alt="The Comments button icon in GitBook"></picture> ，位置在 [章节标题栏](https://gitbook.com/docs/documentation/zh/can-kao/gitbook-ui.md#space-header).

在此添加评论会将评论附加到整个页面。你也可以通过将鼠标悬停在某个块上，然后点击右侧出现的内容图标来对特定块发表评论。

如果你拥有 `comment` 角色，就可以直接在页面和内容块上发表评论，无需创建更改请求。

输入 `@` 符号，后面跟上队友的姓名，即可标记队友。

{% hint style="info" %}
访客可以直接评论，但他们无法查看或提及组织中的其他人。
{% endhint %}

### 评论线程

你可以回复任何评论，与队友展开对话，将其变成一个讨论线程。

你也可以点击你想要回应的消息或线程上的表情按钮，为任何评论留下一个表情反应。

### 解决评论

如果你已处理完某个评论串或想法，可以随时 **解决** 评论。解决评论后，它会在界面中隐藏，但仍可在该部分评论面板的 **已解决** 选项卡中访问。


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://gitbook.com/docs/documentation/zh/collaborate/comments.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
