From 098b520129384976a9d40b074452e0ed0aaca574 Mon Sep 17 00:00:00 2001 From: Eunjae Lee Date: Wed, 23 Jul 2025 15:08:09 +0200 Subject: [PATCH] chore: add review rule for agents to avoid large PRs (#22690) --- .cursor/rules/review.mdc | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/.cursor/rules/review.mdc b/.cursor/rules/review.mdc index 4344e2c39e..68b1db0882 100644 --- a/.cursor/rules/review.mdc +++ b/.cursor/rules/review.mdc @@ -19,3 +19,10 @@ - "summary" fields do not end with a period - "summary" fields are written in proper American english - When changes to API v2 or v1 are made, ensure there are no breaking changes on existing endpoints. Instead, there needs to be a newly versioned endpoint with the updated functionality but the old one must remain functional +- For large pull requests (>500 lines changed or >10 files touched), advise splitting into smaller, focused PRs: + - Split by feature boundaries: separate different features or user stories + - Split by layer/component: frontend changes, backend changes, database migrations, and tests in separate PRs + - Split by dependency chain: create PRs that can be merged sequentially + - Split by file/module: group related file changes together + - Suggested pattern: Database migrations → Backend logic → Frontend components → Integration tests + - Benefits: easier review, faster feedback, reduced conflicts, easier rollback, better history