I wanted Python repository health checks without flooding the main Codex thread with raw `uv`, `ruff`, `pytest`, and `ty` output. So I built a subagent-backed skill that inspects the repo, runs the usual commands, and returns a compact report with clear pass, warn, and fail signals.
I already had reusable `uv`-first instructions for Claude Code and Codex. I have now added the Cursor path too: generate a rule from the same source guidance so Cursor stays on the same Python workflow.
I kept noticing coding agents drifting into `pip install`, raw `python`, and hand-edited dependency files in Python projects. So I built a small repo with reusable `CLAUDE.md` and `AGENTS.md` guidelines that push both Claude and Codex toward a consistent `uv` workflow.
A talk on understanding and using functions in Python — what they are, why they matter, and how to start writing your own — at PyLadies Budapest.
Still relying on print statements to debug your Python code? There’s a much better way: clean, structured, multi-destination, non-blocking logging.