Recently Written · git

ai-config

One canonical AI agent config (rules, skills, MCP servers) rendered into Claude Code, Codex, Copilot CLI and Antigravity by acsync

git clone https://github.com/equwal/ai-config

Log | Files | Refs


commit 365fb44d68c673ab93e0efe1e9607271961096ef
equwal <13551856+equwal@users.noreply.github.com>
2026-10-04 19:24:11 -0700

Add no-bak rule: git, not .bak files; temp dir when git is impossible

 acsync.toml      | 1 +
 rules/install.md | 2 +-
 rules/no-bak.md  | 7 +++++++
 3 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/acsync.toml b/acsync.toml
index 0c8c7e0..66dc2de 100644
--- a/acsync.toml
+++ b/acsync.toml
@@ -46,6 +46,7 @@ adopt_heading = "## MANDATORY: Undo commands are copy-only"
 [rules.cleanup]
 [rules.email-patches]
 [rules.hand-written]
+[rules.no-bak]
 
 # ---------- skills (all 8 skills folders) ----------
 # ste-writing: retired; must not exist in any skills folder.
diff --git a/rules/install.md b/rules/install.md
index da549f1..464c767 100644
--- a/rules/install.md
+++ b/rules/install.md
@@ -11,7 +11,7 @@ An install task is done only when every AI on both computers has the thing. That
 
 Computers: the Windows PC, and the Linux desktop `g` (${g_ip}, `ssh ${g_user}@${g_ip}`).
 
-- Install, register, or copy the thing for each of the 8 targets. Back up each config file before you edit it.
+- Install, register, or copy the thing for each of the 8 targets. Commit each config file in its git repo before you edit it (rule no-bak).
 - If the thing has a GitHub gist (for example the agent-manager skill), edit the gist too, so that it matches the installed copy: `gh gist edit <id> -f <file> <local file>`.
 - If an AI is not installed on a computer yet, write its config files anyway, so that it gets them at its first start. Report each missing AI.
 - Verify each target with a command. Report one line for each of the 8 targets: done, or blocked with the cause.
diff --git a/rules/no-bak.md b/rules/no-bak.md
new file mode 100644
index 0000000..aa52edc
--- /dev/null
+++ b/rules/no-bak.md
@@ -0,0 +1,7 @@
+## MANDATORY: Git, not .bak files
+
+Never create `.bak`, `.orig`, `~`, or similar backup copies next to the file you edit.
+
+- Use git. Commit the file before you edit it, or check that it is already committed and clean.
+- If the file is not in a git repo and you cannot put it in one, copy it into a new folder under the system temp directory: `mktemp -d` on Linux, `$env:TEMP` on Windows. Never put the backup in the file tree.
+- Name the backup path in your report.