Ruff

Workflow

1. Detect current Ruff version, Python targets, and existing lint/format tools.
2. Set one canonical Ruff configuration and inheritance strategy.
3. Select rule families in adoption layers to control migration noise.
4. Configure formatter behavior and notebook handling.
5. Integrate editor, pre-commit, and CI with version pinning.
6. Apply safe autofixes first, then isolate unsafe changes.
7. Tune cache and file discovery for monorepo-scale performance.

Preflight (Ask / Check First)

• Check whether the repo already uses pyproject.toml, ruff.toml, or .ruff.toml.
• Check whether Black, Flake8 plugins, or isort are already enforced in CI.
• Check target Python versions across runtime and tooling.
• Check whether Jupyter notebooks are in scope for linting or formatting.
• Check whether the team wants preview features or strict stability.