Let Claude run per-crate/feature tests
What the developer wrote
Authored by Elias Rohrer
Let Claude run per-crate/feature tests
Previously, we instructed Claude to always run `./ci/ci-tests.sh` which
doesn't seem to work well in practice, as he seems to also employ some
kind of timeout, potentially leading to him getting stuck.
Here we update `CLAUDE.md` accordingly, having him only run `cargo test`
What changed, and why it matters
This commit only updates internal documentation (CLAUDE.md) that tells an AI coding assistant how to run tests. It changes the recommended test command from a long CI script to a shorter cargo test command. There is no code change, no security fix, and no security relevance.
No security action needed. This is a routine documentation update.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies CLAUDE.md, replacing the instruction to run ./ci/ci-tests.sh with guidance to run cargo +1.75.0 test for affected crates/features and optionally prompt the user before running the full CI script. This is a developer workflow/documentation tweak only.
Changed components
CLAUDE.md (developer documentation)Inspect captured patch +5 / −1
diff --git a/CLAUDE.md b/CLAUDE.md
index 611322c..f87bc66 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -10,7 +10,11 @@ See [README.md](README.md) for the workspace layout and [ARCH.md](ARCH.md) for s
## Development Rules
-- Always ensure tests pass before committing. To this end, you should run the test suite via `./ci/ci-tests.sh`.
+- Always ensure tests pass before committing. To this end, you should run
+ `cargo +1.75.0 test` for all affected crates and/or features. Upon completion
+ of the full task you might prompt the user whether they want you to run the
+ full CI tests via `./ci/ci-tests.sh`. Note however that this script will run
+ for a very long time, so please don't timeout when you do.
- Run `cargo +1.75.0 fmt --all` after every code change
- Never add new dependencies unless explicitly requested
- Please always disclose the use of any AI tools in commit messages and PR descriptions using a `Co-Authored-By:` line.
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.