From 872901007ecd7ff34afddc51da121aba0493a63a Mon Sep 17 00:00:00 2001
From: Ryan Yin <xiaoyin_c@qq.com>
Date: Thu, 1 Oct 2026 11:33:14 +0800
Subject: [PATCH] docs(agents): use terraform plan, drop nonexistent helm diff

---
 agents/AGENTS.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/agents/AGENTS.md b/agents/AGENTS.md
index a08fdf0c..4be7dda2 100644
--- a/agents/AGENTS.md
+++ b/agents/AGENTS.md
@@ -73,11 +73,11 @@ For an impactful change, follow these steps in order, scaled to its risk:
    checks when their evidence remains valid for the current action; do not repeat them just because
    another action is needed. Refresh checks when the target, account, context, or relevant state
    changes, or the evidence is stale, incomplete, uncertain, or contradicted. Stop on a mismatch.
-3. **Preview** with plan, diff, or dry-run where available (e.g. `tofu plan`, `kubectl diff`,
-   `helm diff`). Review the current changes; any later input change requires a new preview. When a
-   diff adequately previews the action (e.g. an ordinary non-force branch push or an issue/PR
-   title/description edit), do not add a dry-run unless it checks something the diff does not cover
-   (e.g. rewritten history or uncertain remote state).
+3. **Preview** with plan, diff, or dry-run where available (e.g. `terraform plan`, `kubectl diff`).
+   Review the current changes; any later input change requires a new preview. When a diff adequately
+   previews the action (e.g. an ordinary non-force branch push or an issue/PR title/description
+   edit), do not add a dry-run unless it checks something the diff does not cover (e.g. rewritten
+   history or uncertain remote state).
 4. **Plan the way back.** Keep the blast radius small, know how to undo the change, and prefer
    recoverable forms (e.g. `git push --force-with-lease`, `git branch -d`). If it cannot be undone,
    say so and get authorization that acknowledges it.