Follow-up to #1054, which turned on lint, type-check and test for the Python under skills/ but deliberately skipped the formatter:
[tool.magpie.checks]
skip = ["ruff-format"]
The reason is sound and recorded in skills/pyproject.toml: folding a mechanical reformat into the change that turns the checks on buries the reviewable part behind churn nobody can read line by line. This issue exists so the skip does not quietly become permanent — the comment says "after which this skip can be deleted" and nothing was tracking it.
Size of the job
Measured on the #1054 branch with uv run ruff format --diff under skills/:
|
|
| Files reformatted |
6 |
| Lines removed |
94 |
| Lines added |
187 |
| Total churn |
269 |
All of it is the formatter reflowing things that are merely long — set literals like MACOS_X64 in ci-runner-audit/scripts/scan_ci_runners.py exploded one element per line, and long re.compile(...) constants wrapped across lines. No logic moves.
What to do
- Run
uv run --directory skills ruff format . and commit the result on its own, touching nothing else.
- Delete the
[tool.magpie.checks] block from skills/pyproject.toml — with ruff-format no longer skipped, run-workspace-check.sh picks it up automatically from the [tool.ruff] section already present.
- Confirm
prek run --all-files is green.
Why it is a good first issue
The change is entirely mechanical and the tooling decides the outcome — there is nothing to design. The only judgement needed is not mixing anything else into the commit, which is the point of doing it separately.
Worth doing reasonably soon: every new script added under skills/ before this lands is written against an unformatted baseline, so the eventual diff only grows.
Follow-up to #1054, which turned on lint, type-check and test for the Python under
skills/but deliberately skipped the formatter:The reason is sound and recorded in
skills/pyproject.toml: folding a mechanical reformat into the change that turns the checks on buries the reviewable part behind churn nobody can read line by line. This issue exists so the skip does not quietly become permanent — the comment says "after which this skip can be deleted" and nothing was tracking it.Size of the job
Measured on the #1054 branch with
uv run ruff format --diffunderskills/:All of it is the formatter reflowing things that are merely long — set literals like
MACOS_X64inci-runner-audit/scripts/scan_ci_runners.pyexploded one element per line, and longre.compile(...)constants wrapped across lines. No logic moves.What to do
uv run --directory skills ruff format .and commit the result on its own, touching nothing else.[tool.magpie.checks]block fromskills/pyproject.toml— withruff-formatno longer skipped,run-workspace-check.shpicks it up automatically from the[tool.ruff]section already present.prek run --all-filesis green.Why it is a good first issue
The change is entirely mechanical and the tooling decides the outcome — there is nothing to design. The only judgement needed is not mixing anything else into the commit, which is the point of doing it separately.
Worth doing reasonably soon: every new script added under
skills/before this lands is written against an unformatted baseline, so the eventual diff only grows.