agentleFS
joshuadavidthomasjoshuadavidthomas/django-language-server/.agents/skills/djls-testing/SKILL.md

djls-testing

Skill207 starsChanged yesterdayApache-2.0View on GitHub

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.

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this when validating changes or fixing test failures.

    line 8
  2. Distinctive:

    All tests must pass. Fix failures instead of dismissing them as pre-existing or unrelated.

    line 32
  3. Very specific:

    If corpus tests fail, run just corpus sync and fix/update snapshots as needed.

    line 33
  4. Very specific:

    Before pushing, run just clippy, just fmt, and just lint.

    line 34
  5. Very specific:

    Use insta for template parser snapshots.

    line 39
  6. Distinctive:

    Add cases to existing test modules.

    line 40
  7. Distinctive:

    After changing serialized types, run:

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

DJLS Testing

Use this when validating changes or fixing test failures.

Common commands

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.

Rules

  • All tests must pass. Fix failures instead of dismissing them as pre-existing or unrelated.
  • If corpus tests fail, run just corpus sync and fix/update snapshots as needed.
  • Before pushing, run just clippy, just fmt, and just lint.
  • Python inspector changes must be tested against all supported Django versions; see DJ_VERSIONS in noxfile.py.

Snapshots

  • Use insta for template parser snapshots.
  • Add cases to existing test modules; do not create standalone test files.
  • After changing serialized types, run:
cargo insta test --accept --unreferenced delete

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.