# Comments

Comments are the best way to add little notes or reminders throughout your code. These can describe the purpose of a section or even list some changes you want to make in the future.

Skript will treat anything after an octothorpe (hasgtag), (`#`) as a comment. Comments are not code, in fact, Skript will just completely ignore all characters in a line after them! Unfortunately, this means if you're not careful, you can break code. If you put an octothorpe in a string, it will make the rest of the line a comment. To fix this, double them (`##`) whenever you don't want to add a comment.

{% hint style="info" %}
Describe sections, not lines. Comments are meant to be a quick summary. If it's for one line, you might as well read the line. You save time most effectively when using comments to summarise or describe the purpose of multiple lines.
{% endhint %}

{% hint style="warning" %}
There is such a thing as over-commenting. You don't need comments everywhere in your scripts, just in particularly dense or confusing sections. Adding too many comments can actually decrease readability instead of increasing it.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://x8ight.gitbook.io/syntask/organisation/comments.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.