AGENTS: Add instruction to format and check Python files with ruff after editing

[potiuk]

Add instruction to AGENTS.md Coding Standards to always run ruff format and ruff check --fix on Python files immediately after writing or editing them.

---

Was generative AI tooling used to co-author this PR?

• Yes — Claude Opus 4.6 (1M context)

Generated-by: Claude Opus 4.6 (1M context) following the guidelines

[shivaam]

PR checklist already requires running static checks before pushing. Wouldn't running those once before commit/PR be sufficient rather than after every file edit?
Curious if there's a specific failure mode this is targeting that the batch approach doesn't catch.

[potiuk]

PR checklist already requires running static checks before pushing. Wouldn't running those once before commit/PR be sufficient rather than after every file edit? Curious if there's a specific failure mode this is targeting that the batch approach doesn't catch.

Yes - ruff is VERY fast and can be done immediately, on the other hand runnig prek for the change takes a bit of time and often what happens when you run the checks after edit they fail first and then the agent looks at the output, re-adds the file and re-runs prek check. This takes usually a bit less than minute more for re-run and I get it practically every time when some files were edited.

By adding ruff at modification time - when everything else is fine, this will result in no rerun needed. So prek will only be run once and succeed. So this is rally an optimisation of speed of processing.

[shivaam]

PR checklist already requires running static checks before pushing. Wouldn't running those once before commit/PR be sufficient rather than after every file edit? Curious if there's a specific failure mode this is targeting that the batch approach doesn't catch.

Yes - ruff is VERY fast and can be done immediately, on the other hand runnig prek for the change takes a bit of time and often what happens when you run the checks after edit they fail first and then the agent looks at the output, re-adds the file and re-runs prek check. This takes usually a bit less than minute more for re-run and I get it practically every time when some files were edited.

By adding ruff at modification time - when everything else is fine, this will result in no rerun needed. So prek will only be run once and succeed. So this is rally an optimisation of speed of processing.

That makes sense.