From 8cd6378c816a7cd224792e389c60f24e2312808e Mon Sep 17 00:00:00 2001 From: seto Date: Mon, 13 Apr 2026 16:19:01 +0900 Subject: [PATCH] =?UTF-8?q?fix:=20cubic-dev-ai=20round=203=20=E2=80=94=20S?= =?UTF-8?q?KILL.md=20consistency?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit P2: Description now says "Edit/Write/Bash (including MultiEdit)" instead of listing MultiEdit as a separate top-level gate P2: Write Gate and Anti-Patterns now use same "redacted or synthetic values" wording as Edit Gate (was still "cat one real record") All 3 gate doc sections now consistent. 9/9 tests pass. Co-Authored-By: Claude Opus 4.6 (1M context) --- skills/gateguard/SKILL.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/skills/gateguard/SKILL.md b/skills/gateguard/SKILL.md index 903e9145..a15e1fe7 100644 --- a/skills/gateguard/SKILL.md +++ b/skills/gateguard/SKILL.md @@ -1,6 +1,6 @@ --- name: gateguard -description: Fact-forcing gate that blocks Edit/MultiEdit/Write/Bash and demands concrete investigation (importers, data schemas, user instruction) before allowing the action. Measurably improves output quality by +2.25 points vs ungated agents. +description: Fact-forcing gate that blocks Edit/Write/Bash (including MultiEdit) and demands concrete investigation (importers, data schemas, user instruction) before allowing the action. Measurably improves output quality by +2.25 points vs ungated agents. origin: community --- @@ -64,7 +64,8 @@ Before creating {file_path}, present these facts: 1. Name the file(s) and line(s) that will call this new file 2. Confirm no existing file serves the same purpose (use Glob) -3. If this file reads/writes data files, cat one real record +3. If this file reads/writes data files, show field names, structure, + and date format (use redacted or synthetic values, not raw production data) 4. Quote the user's current instruction verbatim ``` @@ -102,7 +103,7 @@ This adds `.gateguard.yml` for per-project configuration (custom messages, ignor ## Anti-Patterns - **Don't use self-evaluation instead.** "Are you sure?" always gets "yes." This is experimentally verified. -- **Don't skip the data schema check.** Both A/B test agents assumed ISO-8601 dates when real data used `%Y/%m/%d %H:%M`. Checking one real record prevents this entire class of bugs. +- **Don't skip the data schema check.** Both A/B test agents assumed ISO-8601 dates when real data used `%Y/%m/%d %H:%M`. Checking data structure (with redacted values) prevents this entire class of bugs. - **Don't gate every single Bash command.** Routine bash gates once per session. Destructive bash gates every time. This balance avoids slowdown while catching real risks. ## Best Practices