> For the complete documentation index, see [llms.txt](https://docs.tessl.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tessl.io/automations.md). # Automations - [Automations overview](https://docs.tessl.io/automations/overview.md): Automate recurring work by declaring schedules in your tessl.json and pushing them to your default branch. - [Schedules](https://docs.tessl.io/automations/overview/overview.md): No CI setup, no GitHub Actions config. Declare a schedule in your tessl.json, push to your default branch, and Tessl runs it for you. - [Validate schedules in CI](https://docs.tessl.io/automations/overview/overview/validate-in-ci.md): Add tessl schedule validation to your continuous integration workflow. - [Example Schedules](https://docs.tessl.io/automations/overview/overview/example-schedules.md) - [Keep docs in sync](https://docs.tessl.io/automations/overview/overview/example-schedules/use-case-docs-audit.md): Keep your docs in sync with your code, automatically. A scheduled docs audit checks whether the docs still match the code and opens a PR when they have drifted. - [Weekly changelog](https://docs.tessl.io/automations/overview/overview/example-schedules/use-case-changelog.md): Get a changelog draft every week without anyone remembering to write it. A scheduled changelog writer scans the week's merged PRs and opens a PR with the draft. - [Review pattern mining](https://docs.tessl.io/automations/overview/overview/example-schedules/use-case-review-miner.md): Stop repeating the same code-review comment. A scheduled review miner reads recent reviews, finds the feedback that keeps coming up, and proposes a lint rule for it. - [Test health monitor](https://docs.tessl.io/automations/overview/overview/example-schedules/use-case-test-health.md): Catch flaky tests before everyone learns to ignore them. A scheduled test health monitor finds flaky or repeatedly failing tests and files a ticket for each one. - [Release readiness check](https://docs.tessl.io/automations/overview/overview/example-schedules/use-case-release-check.md): Find release problems while there is still time to fix them. A scheduled release check verifies migrations, feature flags, the changelog, and the docs before each release window. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.tessl.io/automations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.