From b3468095c980d8647c7671e492ebbd3d8cdf7aa1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=D0=92=D0=B8=D1=82=D0=B0=D0=BB=D0=B8=D0=B9=20=D0=9D=D0=B8?= =?UTF-8?q?=D0=BA=D0=B8=D1=82=D0=B5=D0=BD=D0=BA=D0=BE?= Date: Fri, 21 Aug 2026 15:42:04 +0300 Subject: [PATCH] docs(rules): authorize Eltex merge-request review writes --- home-configs/GLOBAL_RULES.md | 1 + 1 file changed, 1 insertion(+) diff --git a/home-configs/GLOBAL_RULES.md b/home-configs/GLOBAL_RULES.md index db6df97..aa3ba42 100644 --- a/home-configs/GLOBAL_RULES.md +++ b/home-configs/GLOBAL_RULES.md @@ -23,6 +23,7 @@ Use these defaults across projects, then apply any more specific repository inst - For requests to answer, explain, review, diagnose, or plan, inspect the relevant materials and report the result. Do not implement changes unless the request also asks for them. - For requests to change, build, or fix, perform safe in-scope local edits and validation without asking for routine confirmation. - Ask before destructive or difficult-to-recover actions, external writes or publication, purchases, or a material expansion of scope. +- Exception for Eltex merge-request reviews: a bare review request or explicit `eltex-review` invocation authorizes the skill's documented GitLab writes, including inline discussions, approval, and its thank-you note. Explicit chat-only wording keeps the review read-only. - Preserve unrelated user changes and adapt to a dirty working tree. Never discard or overwrite work you did not create. ## 4. Plan and Verify Proportionally