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

djls-ruff-ast

Skill207 starsChanged yesterdayApache-2.0View on GitHub

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.

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 before editing djls-extraction or code that consumes Ruff Python AST nodes.

    line 8
  2. Very specific:

    Use let, not if let.

    line 19

≈ “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 Ruff AST

Use this before editing djls-extraction or code that consumes Ruff Python AST nodes.

Known API shapes

  • Parse modules with ruff_python_parser::parse_module(source) and call .into_syntax() for ModModule AST.
  • Function defaults are per-parameter. There is no top-level defaults field.
    • Use ParameterWithDefault { parameter, default: Option<Box<Expr>> }.
  • StmtWhile.test, StmtIf.test, and similar fields are Box<Expr>.
    • Dereference with &* for pattern matching.
  • FStringValue uses .iter(), not .parts(), for FStringPart iteration.
  • ExceptHandler::ExceptHandler is irrefutable.
    • Use let, not if let.

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.