> ## Documentation Index
> Fetch the complete documentation index at: https://docs.assert.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Cluster Customization

> Configure how Assert groups changes into clusters

Clustering works without configuration. You can add instructions for a repository
or for a single pull request, such as keeping migrations with their queries or
tests with the code they cover.

## Repository instructions

Add **`.assert/CLUSTERING.md`** to your base branch:

```md .assert/CLUSTERING.md theme={null}
Keep tests with the behavior they cover.
Group each database migration with the queries and code that use it.
Separate unrelated documentation updates from implementation changes.
Use feature-oriented titles instead of directory names.
```

Assert reads this file from the PR's **base commit**, so it only applies once it's
merged into the base branch.

## Pull request instructions

To give instructions for one pull request, add a block to its GitHub description:

```md theme={null}
<!-- assert:clustering -->
Group the API rename and its callers together across packages.
Keep the unrelated cache fix in a separate cluster.
<!-- /assert:clustering -->
```

Pull request instructions take priority over repository instructions. Keep the
regular PR summary outside the block.

## Tips

Describe what belongs together and why. Short instructions with concrete examples
work better than long lists of rules.

Changes take effect the next time clustering runs, such as after a push; editing
the description alone doesn't regenerate clusters. Assert treats instructions as
guidance and may still split a large group to keep it reviewable.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.