> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/quality-control/rules/create-quality-rule.md).

# Create Quality Rule

To create a new Quality Rule:

1. Navigate to **`Rules`** -> **`Quality Rules`**
2. Click on **`Add Rule`**
3. Enter the basic details:
   1. **`Rule Name`** - Name of the rule
   2. **`Rule Severity`** - Severity of the rule
   3. **`Rule Category`** - Category of the rule
   4. **`Language`** - Language for which the rule is applicable. E.g.: Mule, API
   5. **`Rule Tags`** - Tags associated with the rule. Tags can be used to filter issues\
       

      <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FgPo1Bai9rPn4BTkMXMYw%2Fcreate-rule1.png?alt=media&amp;token=c519da90-11d6-4533-8913-c16d922d787f" alt=""><figcaption></figcaption></figure>
   6. **`Rule Description`** - Description of the rule in Markdown format <br>

      <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FrcqbFPqqjmSFXPeXbejJ%2Fcreate-rule2.png?alt=media&amp;token=ed0e7bcd-d32c-4525-8ae0-60cf5f2f609c" alt=""><figcaption></figcaption></figure>
   7. **`Rule Definition`** - Definition of the rule. Rules are specified in Groovy
   8. **`Auto Fix Definition`** - Auto Fix Definition of the rule. Rules are specified in Groovy <br>

      <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fw3swtgpcHMY0wKJKwGZN%2Fcreate-rule3.png?alt=media&amp;token=42995f03-6007-4510-9ce8-e909a74ecf0a" alt=""><figcaption></figcaption></figure>
4. Click on **`Submit`** to create the rule definition

### See Also

* [Quality Profiles](/product-guides/integral-zone/iz-suite/quality-control/profiles/quality-profiles.md)
* [Metric Profiles](/product-guides/integral-zone/iz-suite/quality-control/profiles/metric-profiles.md)
* [Quality Rules](/product-guides/integral-zone/iz-suite/quality-control/rules/quality-rules.md)
* [Metric Rules](/product-guides/integral-zone/iz-suite/quality-control/rules/metric-rules.md)


---

# 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://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/quality-control/rules/create-quality-rule.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.