GateGuard — Fact-Forcing Pre-Action Gate

When to Activate

• Working on any codebase where file edits affect multiple modules
• Projects with data files that have specific schemas or date formats
• Teams where AI-generated code must match existing patterns
• Any workflow where Claude tends to guess instead of investigating

Core Concept

1. DENY  — block the first Edit/Write/Bash attempt
2. FORCE — tell the model exactly which facts to gather
3. ALLOW — permit retry after facts are presented

Evidence

Gate Types

Edit / MultiEdit Gate (first edit per file)

Before editing {file_path}, present these facts:

1. List ALL files that import/require this file (use Grep)
2. List the public functions/classes affected by this change
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

Write Gate (first new file creation)

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, show field names, structure,
   and date format (use redacted or synthetic values, not raw production data)
4. Quote the user's current instruction verbatim

Destructive Bash Gate (every destructive command)

rm -rf

git reset --hard

git push --force

drop table

1. List all files/data this command will modify or delete
2. Write a one-line rollback procedure
3. Quote the user's current instruction verbatim

Routine Bash Gate (once per session)

Quote the user's current instruction verbatim.

Quick Start

Option A: Use the ECC hook (zero install)

scripts/hooks/gateguard-fact-force.js

Option B: Full package with config

pip install gateguard-ai
gateguard init

.gateguard.yml

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 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

• Let the gate fire naturally. Don't try to pre-answer the gate questions — the investigation itself is what improves quality.
• Customize gate messages for your domain. If your project has specific conventions, add them to the gate prompts.
• Use

  .gateguard.yml

  to ignore paths like

  .venv/

  ,

  node_modules/

  ,

  .git/

  .

Related Skills

• safety-guard

  — Runtime safety checks (complementary, not overlapping)

• code-reviewer

  — Post-edit review (GateGuard is pre-edit investigation)