# Linting & formatting

A step of the [Cloud application](https://gradus.kazet.blog/tree/cloud-application) tree on Gradus, in the Build & ship area: Config, lint, releases, IaC.

Page: https://gradus.kazet.blog/tree/cloud-application/step/lint-and-format

Add a linter and formatter with a shared config, run them in CI and on commit, so style never comes up in review.

Usually comes after: [Project structure & config](https://gradus.kazet.blog/tree/cloud-application/step/project-structure).

Leads to: [Commit conventions & review](https://gradus.kazet.blog/tree/cloud-application/step/commit-conventions), [Automated dependency updates](https://gradus.kazet.blog/tree/cloud-application/step/dependency-updates).

## Prompt for your AI assistant

```
Set up a linter and a code formatter for this project with a shared config, add a pre-commit hook that runs them and make the CI workflow fail on lint errors.
```

Every step of the tree: https://gradus.kazet.blog/tree/cloud-application/llms.txt