| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 3 | 1 | 0% |
| Commands | 0 | 3 | 0 | 0% |
| Section tags | 2 | 2 | 1 | 40% |
What each file covers
Sections
0 shared · 3 only in A · 1 only in B- − AI Service Test Instructions
- − Commands
- − Rules
- + Documentation Rules
Commands
0 shared · 3 only in A · 0 only in B- − python -m pytest
- − python -m pytest tests/test_health.py
- − python -m pytest tests/test_consents.py
Section tags
2 shared · 2 only in A · 1 only in B- − test
- − agent-behaviour
- + docs
- code-style
- do-not
Line diff
Aledon8/OpenLeukemia · ai-service/tests/CLAUDE.md
@@ −1 @@
1# AI Service Test Instructions
2
3## Commands
4
5Run from `ai-service/`:
6
7```sh
8python -m pytest
9python -m pytest tests/test_health.py
10python -m pytest tests/test_consents.py
11```
12
13## Rules
14
15- Keep tests focused on externally visible behavior and domain contracts.
16- Cover consent and privacy-sensitive behavior conservatively.
17- Prefer clear test names that describe the expected behavior.
18- Add regression tests when fixing bugs in API routes, schemas, or domain services.
19- If a test fails, fix the root cause and rerun the smallest failing test before broader checks.
20
Aledon8/OpenLeukemia · .cursor/rules/docs.mdc
@@ +1 @@
1---
2description: Documentation writing rules
3globs:
4 - "docs/**/*.md"
5 - "*.md"
6alwaysApply: false
7---
8
9# Documentation Rules
10
11- Write in plain, precise language for patients, contributors, and reviewers.
12- Keep privacy, consent, patient control, and non-diagnostic AI limits visible.
13- Prefer durable project facts over session-specific notes.
14- Match the structure and voice of nearby documents.
15
@@ −1 +1 @@
1−# AI Service Test Instructions
1+---
2+description: Documentation writing rules
3+globs:
4+ - "docs/**/*.md"
5+ - "*.md"
6+alwaysApply: false
7+---
28
3−## Commands
9+# Documentation Rules
410
5−Run from `ai-service/`:
6−
7−```sh
8−python -m pytest
9−python -m pytest tests/test_health.py
10−python -m pytest tests/test_consents.py
11−```
12−
13−## Rules
14−
15−- Keep tests focused on externally visible behavior and domain contracts.
16−- Cover consent and privacy-sensitive behavior conservatively.
17−- Prefer clear test names that describe the expected behavior.
18−- Add regression tests when fixing bugs in API routes, schemas, or domain services.
19−- If a test fails, fix the root cause and rerun the smallest failing test before broader checks.
11+- Write in plain, precise language for patients, contributors, and reviewers.
12+- Keep privacy, consent, patient control, and non-diagnostic AI limits visible.
13+- Prefer durable project facts over session-specific notes.
14+- Match the structure and voice of nearby documents.
2015
