docs(gateguard): point path exemptions at GATEGUARD_EXEMPT_GLOBS (#2573)

The skill told readers to ignore paths through .gateguard.yml, but the ECC hook has no YAML config loader; its documented controls are the GATEGUARD_* environment variables. Clarify that the optional gateguard-ai CLI owns that file.

Co-Authored-By: TRAE <noreply@trae.ai>
This commit is contained in:
huangpz6andTRAE committed 2026-11-04 11:32:58 +08:00
1 parent b38be6a7f6
commit 9142afa7ce
1 file changed
+4 -2
+4 -2
View File
@@ -691,7 +691,9 @@ pip install gateguard-ai
gateguard init
```
This adds `.gateguard.yml` for per-project configuration (custom messages, ignore paths, gate toggles).
That CLI writes `.gateguard.yml` for its own runtime. The ECC hook shipped in this
repository does **not** read that file; configure it with the `GATEGUARD_*`
environment variables documented above.
## Anti-Patterns
@@ -703,7 +705,7 @@ This adds `.gateguard.yml` for per-project configuration (custom messages, ignor
- Let the gate fire naturally. Don't try to pre-answer the gate questions — the investigation itself is what improves quality. A real search for the target before editing is investigation, and is credited (see [What Counts as Already Done](#what-counts-as-already-done)).
- 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/`.
- Use `GATEGUARD_EXEMPT_GLOBS` to skip first-touch checks for paths like `.venv/`, `node_modules/` and `.git/`; the hook does not read `.gateguard.yml`.
## Related Skills