docs: neutral agent wording, PR target, and pre-push CI rule
- Describe the file's audience as "AI coding agents" rather than naming a specific third-party tool. - Require pull requests to target the development branch (main is release-only). - Require the full CI gate (fmt + clippy + test) to pass locally before pushing a branch or opening a pull request. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014f6zfWDT1v5TeSpA29rEyx
Claude committed
Jul 1, 2026 at 09:34 UTC
609c035bc18baf86fa11bdf0af8aac426cf6fdc6
1 file changed
+14
-2
CLAUDE.md
+14
-2
@@ -1,6 +1,6 @@
1
# CLAUDE.md
2
3
-This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
3
+This file provides guidance to AI coding agents when working with code in this repository.
4
5
## What this is
6
@@ -22,7 +22,19 @@ Before the TTY/ACP split, `main` also dispatches the account subcommands `sigit
22
**IMPORTANT — branch naming:** Name every working branch after the *changes it contains*, not
23
after a task, ticket, or session id. Use a short, descriptive, kebab-case slug so the branch is
24
self-explanatory from its name alone (e.g. `claude/agent-tools-multiedit-glob-todos-remember`,
25
-not `claude/code-feature-parity-q003hm`).
25
+not `claude/task-q003hm`).
26
+
27
+**IMPORTANT — pull request target:** Always open pull requests against the `development` branch,
28
+never `main`. `main` is release-only; `development` is where day-to-day work integrates.
29
+
30
+**IMPORTANT — run CI before pushing:** Run the full CI gate locally and confirm it is green
31
+*before* pushing a branch or opening a pull request — never push work that fails these:
32
+
33
+```sh
34
+cargo fmt -- --check # formatting
35
+cargo clippy --tests -- -D warnings # lint (warnings are errors)
36
+cargo test --locked # tests
37
+```
38
39
## Build / test / lint
40