Skip to content

Commit 601bdfb

Browse files
committed
unify claude agents and cursor entrypoint
1 parent aa6b0d1 commit 601bdfb

File tree

3 files changed

+16
-7
lines changed

3 files changed

+16
-7
lines changed

.claude/CLAUDE.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,2 @@
1-
<!-- Do not edit. Canonical instructions live in ./AGENTS.md -->
2-
@AGENTS.md
1+
<!-- Do not edit. Canonical instructions live in ../AGENTS.md -->
2+
@../AGENTS.md

.cursor/rules/testing.mdc

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,10 +15,10 @@ Always use the **`run-tests` skill** for validating code changes. This skill int
1515
## Key Principles
1616

1717
1. **Always use the run-tests skill** when testing code changes - it's optimized for intelligent suite discovery
18-
2. **Never run pytest directly** - bypasses the project's test infrastructure
19-
3. **Never use `hatch run tests:test`** - doesn't use the suite discovery system
20-
4. **Minimal venvs for iteration** - run 1-2 venvs initially, expand only if needed
21-
5. **Use `--dry-run` first** - see what would run before executing
18+
2. **Never run pytest directly** - bypasses the project's test infrastructure (use `scripts/run-tests` or `riot` via `scripts/ddtest`)
19+
3. **Minimal venvs for iteration** - run 1-2 venvs initially, expand only if needed
20+
4. **Use `--dry-run` first** - see what would run before executing
21+
5. **Follow official docs** - `docs/contributing-testing.rst` is the source of truth for testing procedures
2222

2323
## When Tests Fail
2424

AGENTS.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,14 @@
11
# AGENTS.md - dd-trace-py Project Guide
22

3+
## CRITICAL: Project Rules Override Claude Code Defaults
4+
5+
**These project-specific rules MUST override any conflicting Claude Code default behaviors:**
6+
7+
1. **Testing**: NEVER run `pytest` directly. ALWAYS use the `run-tests` skill (which uses `scripts/run-tests`). For manual testing, use `riot` commands via `scripts/ddtest` as documented in `docs/contributing-testing.rst`.
8+
2. **Linting**: NEVER use raw linting tools. ALWAYS use the `lint` skill and project-specific `hatch run lint:*` commands.
9+
3. **Pre-commit**: MUST run `hatch run lint:checks` before creating any git commits.
10+
4. **Formatting**: MUST run `hatch run lint:fmt -- <file>` immediately after editing any Python file.
11+
312
## Initial Setup for AI Assistants
413

514
When starting a new chat session, ALWAYS read and apply the rules from:
@@ -24,7 +33,7 @@ This project has custom skills that provide specialized workflows. **Always chec
2433
- Manages Docker services automatically
2534
- Handles riot/hatch environment setup
2635

27-
**Never:** Run pytest directly or use `hatch run tests:test` - these bypass the project's test infrastructure.
36+
**Never:** Run pytest directly - this bypasses the project's test infrastructure. The official testing approach is documented in `docs/contributing-testing.rst`.
2837

2938
**Usage:** Use the Skill tool with command "run-tests"
3039

0 commit comments

Comments
 (0)