> For the complete documentation index, see [llms.txt](https://docs.tryprotege.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryprotege.com/review/review-tool-concepts/document-review/feedback-cards/comment-generator.md).

# Comment Generator

Each Card has a 💬 button that creates leads to the Comment Generator. This builder is designed to make writing comments for a marketer fast and easy.

When the Comment Generator is opened from a card, you will see:

* **Text to Highlight and Comment on** - this is the original text that is being discussed. Included on all feedback types.
* **Explanation** - The concern or warning for that text. Included on all feedback types.
* **Suggestions (if appropriate)** - Drop in alternative text for a Product Claim or Policy Feedback. be included. Included on Product Claims and select Policy Feedback Cards.
* **Similar Claims (if appropriate)** - For Claims, if there are medium or high match statements, they can be copied the marketer to see.

Check the explanations, suggestions, and similar claims you want to include in the comment. The text box will include the text that you can copy-paste.

On a Mac, you can **\[apple key] + C** to copy. Press add a comment in Google Doc **\[apple key] + option + M** over the relevant text, and then paste **\[apple key] + V.**

![](https://2804394160-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FD9Htw9DUg294GuYmAyyj%2Fuploads%2Fgit-blob-92332c34461a8c08503e60442c08eab6220fd9a5%2FScreenshot%202024-03-02%20at%206.06.16%E2%80%AFPM.png?alt=media)

**Note:** Direct commenting into the Doc from the Protege sidebar is not supported due to Google API limits. A workaround is being developed.


---

# 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://docs.tryprotege.com/review/review-tool-concepts/document-review/feedback-cards/comment-generator.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.
