> For the complete documentation index, see [llms.txt](https://docs.canhav.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.canhav.com/ai-and-ide/checks.md).

# Automated checks

**Studio+.** A workflow in your repository runs Slither (or Aderyn) on the contracts and asks Sourcify whether the deployed addresses are verified, then posts one run per tool to the project. The Review milestone shows the newest run beside the team's own verdict, so a pass reads as proof rather than a tick.

## Setup

The same **GitHub setup** card on Deployments (see [GitHub sync](https://docs.canhav.com/ai-and-ide/github-sync.md)): the write key in the repository secret `CANHAV_PROJECT_KEY`, and the **Checks workflow** downloaded with the project's chain id and the CanHav address filled in, saved at `.github/workflows/canhav-checks.yml`. Set the repository variable `CANHAV_ADERYN` to `1` to run Aderyn instead of Slither. The plain template is `.github-templates/canhav-checks.yml` in the CanHav repository and reads the variables `CANHAV_CHAIN_ID` and `CANHAV_URL` instead.

## What it posts

| Tool              | Summary                                                                              | Result                                                                 |
| ----------------- | ------------------------------------------------------------------------------------ | ---------------------------------------------------------------------- |
| Slither or Aderyn | Counts by severity and up to twenty findings with title, severity and file           | Fail when any high finding, else pass; error when the tool did not run |
| Sourcify          | Per address, full, partial or none, for the addresses in the chain's broadcast files | Pass when every address is verified                                    |

A Sourcify run may only name addresses recorded on Deployments (GitHub sync records them), on the project's chain. The static analysis run shows on the **Static analysis** review pass as "Passed Slither, run 3 Nov" with the counts and the run link; the Sourcify run shows under the testnet contracts on Deployments. The team's verdict stays its own; the run is the evidence beside it.

## Evidence for every account

Every review pass has an evidence field, a run link, a test name or a commit, that any account can fill by hand (`update_project` takes `evidence` on each `kit.review` entry too). It exports with the pass line, so verified evidence is never paid only; Studio+ adds the workflow that fills the automatic runs.

## Related

* [GitHub sync](https://docs.canhav.com/ai-and-ide/github-sync.md)
* [Studio+](https://docs.canhav.com/accounts/studio-plus.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://docs.canhav.com/ai-and-ide/checks.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.
