DJLS Resolver Corpus
SkillDev toolsMaintain the ported ty resolver test corpus in crates/djls-project/tests/resolve.rs. Use when bumping the ruff git pin in the workspace Cargo.toml or when adding/reviewing module-resolution tests.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the DJLS Resolver Corpus skill
What this skill tells your AI
The instructions your AI receives, as published by joshuadavidthomas/django-language-server in .agents/skills/djls-resolver-corpus/SKILL.md and read by ahel’s review.
Use this when maintaining the ported module-resolution tests in crates/djls-project/tests/resolve.rs.
Provenance
crates/djls-project/tests/resolve.rs ports module-resolution tests from ty's resolver in astral-sh/ruff:
crates/ty_module_resolver/src/resolve.rscrates/ty_module_resolver/src/path.rscrates/ty_module_resolver/src/list.rs
Each ported test should carry a // ty:<file>::<name> provenance comment that points back to the source test.
Runtime expectations
Correct expectations where ty's typechecker semantics diverge from CPython's import system:
- Stubs and typeshed never apply.
- Namespace packages resolve.
Ruff pin bumps
When bumping the ruff git rev in the workspace Cargo.toml, diff the ty resolver test files between the old and new revs. Triage added or changed tests into one of these outcomes:
- Port as-is.
- Port with runtime-corrected expectations.
- Skip typechecker-only cases.
Signals
- GitHub stars
- 203
- Forks
- 10
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
djls-resolver-corpus- Source
- github.com/joshuadavidthomas/django-language-server