Code reviews are an essential part of every developer's routine, whether you're getting a PR ready to merge or reviewing someone else's PR.

Have you ever found yourself reading or writing comments like these during a code review?

"Hey Ayushi, can you use the use case? The current ViewModel is communicating with the repo layer, which isn't ideal."
"The UI layer should be as lean as possible; all logic should be moved out."
"Didn't we recently decide on the naming conventions for different classes?"

These are classic examples of code review smells. As engineers, it's tough to remember every architectural detail of all your projects, especially when dealing with a large multi-module app architecture. So, why not automate these checks with lint rules?

In this talk, we'll introduce Konsist—an innovative tool for Android that simplifies the process of writing lint rules by treating them as unit tests, thus eliminating the steep learning curve associated with traditional linters. We will also dive deep into creating lint rules as unit tests and integrating them into CI/CD pipelines for faster development.