メニュー
Use when running tests, fixing failing tests, updating snapshots, syncing corpus data, validating before push, or working with Django matrix testing in django-language-server. Handles cargo, just, nox, insta, corpus, clippy, fmt, and lint commands.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Maintain 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.
Use when editing Django template parser tags, validation errors, diagnostics, environment scanning, inspector data, Python environment inventory, or DJLS domain model code. Handles project-specific semantic and parser conventions.
Use when adding release notes, changelog entries, user-facing changes, internal changelog notes, or preparing a PR/release for django-language-server. Handles Keep a Changelog formatting and entry style.
Use when editing djls-extraction or Rust code that consumes Ruff Python AST APIs, including parse_module, parameters, boxed expressions, f-strings, or exception handlers. Handles known Ruff AST shape gotchas in django-language-server.
Use when editing Salsa inputs, tracked functions, database traits, setters, SemanticDb, crate::Db, invalidation behavior, or incremental computation in django-language-server. Handles project-specific Salsa conventions and required impl updates.
Use when adding or editing crates, Cargo.toml files, workspace dependencies, crate manifests, lints, versions, or project structure in django-language-server. Handles Rust workspace layout, dependency grouping, and new crate setup.
| name | djls-testing |
| description | Use when running tests, fixing failing tests, updating snapshots, syncing corpus data, validating before push, or working with Django matrix testing in django-language-server. Handles cargo, just, nox, insta, corpus, clippy, fmt, and lint commands. |
Use this when validating changes or fixing test failures.
cargo build -q # Build all crates
cargo test -q # Run all tests
cargo test test_name # Run one test by name
cargo test -p crate_name # Test one crate
just test # Run nox/Django matrix
just clippy # Lint with clippy
just fmt # Format code
just lint # Run pre-commit hooks
just corpus lock # Resolve corpus versions and update lockfile
just corpus sync # Download corpus from lockfile
just corpus sync -U # Re-resolve corpus and sync
just corpus clean # Remove synced corpus data
just dev profile <bench> [filter] # Profile a bench with callgrind
Never use cargo doc --open.
just corpus sync and fix/update snapshots as needed.just clippy, just fmt, and just lint.DJ_VERSIONS in noxfile.py.insta for template parser snapshots.cargo insta test --accept --unreferenced delete