From f837de93d8b3fda781598880606e4f58f5ac1e1a Mon Sep 17 00:00:00 2001 From: Shay Date: Wed, 17 Jun 2026 06:53:11 -0700 Subject: [PATCH] create skills/pre-edit-sweep.md - Grok Build skill implementing the Pre-Edit Sweep Protocol at mastery level --- skills/pre-edit-sweep.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 skills/pre-edit-sweep.md diff --git a/skills/pre-edit-sweep.md b/skills/pre-edit-sweep.md new file mode 100644 index 00000000..ea52efb9 --- /dev/null +++ b/skills/pre-edit-sweep.md @@ -0,0 +1,15 @@ +--- +name: pre-edit-sweep +description: Execute full import/call-site + eval/calibration trace before editing sensitive modules. Complements the Versor Coherence Guardian. +triggers: ["pre_edit:algebra/", "pre_edit:field/", "pre_edit:vault/", "pre_edit:generate/", "pre_edit:core/cognition/", "pre_edit:teaching/", "pre_edit:calibration/", "manual"] +auto_invoke: true +--- + +Before editing any module in the triggered paths: + +1. Use file-read and search tool chains to trace **every import** of the target module. +2. Identify **all callers** of the specific function/class being changed. +3. Check `calibration/` and `evals/` for tests exercising the changed path. +4. Only after completing the sweep may you propose or apply edits. + +Your 1M context window exists for this. Use it. Do not guess at impact. \ No newline at end of file