> For the complete documentation index, see [llms.txt](https://help.clausebuddy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clausebuddy.com/summarise-changes/what.md).
# What?
Summarise Changes helps you generate a clear, structured overview of modifications in a document.\
This feature allows you to automatically summarise tracked changes, comments, or textual differences, removing the need to manually review each item.
You can use Summarise Changes in two ways.\
It can create a smart summary of all Track Changes and comments within a single document — including references to where each change occurred, what type of change it was, and a short explanation.\
Alternatively, it can summarise the differences between two versions of a document when no Track Changes were used.
Each summary can be customised by selecting the language, choosing the desired level of detail, grouping the content in different ways, and adding optional instructions for the underlying large language model.
Summarise Changes is designed to support faster reviewing, clearer communication, and more efficient collaboration.
---
# 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://help.clausebuddy.com/summarise-changes/what.md?ask=&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.
