From a2d2073bc908ffad2d1980cd18dcd3a53cb7c0b7 Mon Sep 17 00:00:00 2001
From: jepson2k <55201008+Jepson2k@users.noreply.github.com>
Date: Sat, 9 May 2026 17:12:43 -0400
Subject: [PATCH] docs: drop git-commit and shell-style rules from CLAUDE.md

Removes two CLAUDE.md sections:
- The 'No emoji / no Generated by... / no co-author boilerplate' rule
  under Code Style
- The 'Do NOT use compound cd commands' Shell Command Style section
---
 CLAUDE.md | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/CLAUDE.md b/CLAUDE.md
index 43282a3..815e6c3 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -132,7 +132,6 @@ For streamable commands (`streamable = True`), `do_setup()` also runs at high fr
 ## Code Style
 
 - **Comments**: Describe the final code state, not what changed. Avoid "changed X to Y" or "added this because..." comments.
-- **Git commits/PRs**: No emoji, no "Generated by..." footers, no co-author boilerplate.
 - **Type annotations**: Fix type errors properly instead of using `# type: ignore`. Prefer:
   - `@overload` decorators for functions with different return types based on input
   - `assert` statements to narrow types after None checks
@@ -140,10 +139,6 @@ For streamable commands (`streamable = True`), `do_setup()` also runs at high fr
   - `np.atleast_1d()` or similar to guarantee array returns from numpy functions
   - Only use `# type: ignore` as a last resort for genuine type checker limitations (e.g., numpy's `ArrayLike` being too broad)
 
-## Shell Command Style
-
-- **Do NOT use compound `cd` commands** like `cd foo && git status` or `cd foo && pytest`. Compound commands that cross directories require explicit user approval and slow things down. Instead, issue a standalone `cd foo` command first, then run the action as a separate command. The Bash tool's working directory persists between calls.
-
 ## Testing Guidelines
 
 **When CI tests fail, fix them.** Don't waste time analyzing whether failures are "related to your changes" — just fix all failing tests. The goal is a green CI, not attribution.