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 d3008356b954f50925490710e99b8b8bafe55e3a
equwal <13551856+equwal@users.noreply.github.com>
2026-10-04 05:34:21 -0700

Add rule: email patches upstream; the user writes every email

 acsync.toml            |  1 +
 rules/email-patches.md | 10 ++++++++++
 2 files changed, 11 insertions(+)
diff --git a/acsync.toml b/acsync.toml
index 855d695..fe77d91 100644
--- a/acsync.toml
+++ b/acsync.toml
@@ -44,6 +44,7 @@ machines = ["pc"]        # g never had it; add "g" to roll it out there
 adopt_heading = "## MANDATORY: Undo commands are copy-only"
 [rules.patches]
 [rules.cleanup]
+[rules.email-patches]
 
 # ---------- skills (all 8 skills folders) ----------
 # ste-writing: retired; must not exist in any skills folder.
diff --git a/rules/email-patches.md b/rules/email-patches.md
new file mode 100644
index 0000000..ef16cc4
--- /dev/null
+++ b/rules/email-patches.md
@@ -0,0 +1,10 @@
+## MANDATORY: Email patches upstream; the user writes every email
+
+The user is very keen on sending patches upstream by email (`git format-patch` / `git send-email`) wherever the project accepts them. When a fix or feature is useful to an upstream project, find out how it takes patches (mailing list, maintainer address, `MAINTAINERS`, `CONTRIBUTING`, the project's site) and prepare the email patch. Prefer email over a forge pull request when the project takes both.
+
+The user writes all email text himself. Never write it for him.
+
+- Do the mechanics: rebase the change onto the upstream branch, check it applies and builds, run the project's checks and format tools, find the right recipients, and run `git format-patch` with `--to`/`--cc`.
+- Leave the words to him: the subject line, the commit message body, any cover letter, and replies. Do not draft, suggest, or fill in that text. Open the patch file in his editor or neomutt for him to write, or give him one runnable command that does that.
+- He sends it, or tells you in chat to send that exact file. Never send an email whose text you wrote.
+- This covers all email on his behalf, not only patches: list subscriptions and confirmations are the only messages you may send without his text, and only when he asked for them.