From edfb477d86b7aee33c576ca3ca0e46169db2eac4 Mon Sep 17 00:00:00 2001 From: huangpz6 Date: Wed, 4 Nov 2026 21:38:34 +0800 Subject: [PATCH] docs(gateguard): stop recommending a .git/ exemption (#3866) A literal .git/ pattern does not match ordinary metadata paths such as .git/config, and suggesting .git/** would also bypass first-touch, sensitive-target and hard-link checks. Point the example at generated trees and state the trade-off explicitly. Co-Authored-By: TRAE --- skills/gateguard/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/skills/gateguard/SKILL.md b/skills/gateguard/SKILL.md index 572f88f84..2c7fd02bf 100644 --- a/skills/gateguard/SKILL.md +++ b/skills/gateguard/SKILL.md @@ -705,7 +705,7 @@ environment variables documented above. - 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_EXEMPT_GLOBS` to skip first-touch checks for paths like `.venv/`, `node_modules/` and `.git/`; the hook does not read `.gateguard.yml`. +- Use `GATEGUARD_EXEMPT_GLOBS` to skip first-touch checks for generated trees like `.venv/` and `node_modules/`; the hook does not read `.gateguard.yml`. Do not exempt `.git/**`: a literal `.git/` does not match `.git/config`, and a broad metadata glob would also skip sensitive-target and hard-link checks. ## Related Skills