agentleFS
Sign inStart free
joshuadavidthomasjoshuadavidthomas/django-language-server/.agents/skills/djls-resolver-corpus/SKILL.md

djls-resolver-corpus

Skill207 starsChanged yesterdayApache-2.0View on GitHub

Maintain the ported ty resolver test corpus in crates/djls-project/tests/it/resolve.rs. Use when bumping the ruff git pin in the workspace Cargo.toml or when adding/reviewing module-resolution tests.

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this when maintaining the ported module-resolution tests in crates/djls-project/tests/it/resolve.rs.

    line 8
  2. Very specific:

    When bumping the ruff git rev in the workspace Cargo.toml, diff the ty resolver test files between the old and new revs.

    line 29

≈ “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 Resolver Corpus

Use this when maintaining the ported module-resolution tests in crates/djls-project/tests/it/resolve.rs.

Provenance

crates/djls-project/tests/it/resolve.rs ports module-resolution tests from ty's resolver in astral-sh/ruff:

  • crates/ty_module_resolver/src/resolve.rs
  • crates/ty_module_resolver/src/path.rs
  • crates/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.

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.

Check your setup, free