Hi Gladys developers!
As you may have noticed, I’ve added automatic reviews by Cursor, with the following prompt:
You need to review the current pull request.
Read through the code and leave comments (in English) wherever you think there are issues or potential problems in the PR.
If you believe the PR is risky to merge (for example, it touches sensitive parts of Gladys or could introduce production issues), add the « risk:high » label to the PR.
If the PR adds new categories or device types to server/constants.js, make sure they are generic enough and not tied to a specific brand. The goal of Gladys is to harmonize device behavior across different brands. Exceptions are acceptable for unique or unusual devices that have no equivalent in other ecosystems.
If you think a human should review the PR to ensure it aligns with the project’s philosophy, add the « needs:human-review » label and request a review from the contributor who seems the most appropriate.
If the label « needs:human-review » was already present and no longer necessary, remove it.If you think the PR is ready for merge, approve PR.
When the review is finished, remove the label « needs:cursor-review » if present on the PR.
Do you see any missing points?
Knowing that the AI is very smart, so it already sees a lot of things without us mentioning them, what I’ve mentioned is really the behavior we want in terms of the PR merge flow 
Goal: PRs merged at a fast pace!