Local validation for Python
If ## Project specifics in AGENTS.md names a repository-owned validation
skill, load it first; where it is narrower, it governs.
The commands to run before pushing are in the ## Tooling section of AGENTS.md. This skill covers the detail behind them.
Dependencies
As generated, .github/workflows/test.yml fails with a clear error unless the
repository has a dependency manifest: a pyproject.toml or a
requirements*.txt anywhere in it, or a uv.lock. Those are the files its pip
cache hashes, and actions/setup-python stops with No file ... matched
without one; a setup.py alone does not count. An empty requirements-dev.txt
is enough for a project with no dependencies. The install step below reads only
the root pyproject.toml, requirements-dev.txt and requirements.txt, so a
manifest only in a subdirectory, or in a root file with another name such as
requirements-test.txt, passes this check but installs nothing: keep the
project's dependencies in one of those three root files.
It then installs dependencies in this order; check that repository-owned file for the current steps.
uv.lockexists:uv sync --locked, which installs exactly the locked versions and fails ifuv.lockis out of date withpyproject.toml; runuv lockand commit the result when it does. CI names a declareddevgroup anddevextra explicitly, so a[tool.uv] default-groupssetting cannot leave them out.- Otherwise:
requirements-dev.txtif present, otherwiserequirements.txt. - Otherwise,
pyproject.toml: like uv, CI builds the project only when it declares a[build-system](or has asetup.py, or asetup.cfgwith[metadata]or[options]), and[tool.uv] packageoverrides that. A package installs as-e ., or-e ".[dev]"when a PEP 621[project.optional-dependencies] dev = [...]extra is declared, adding--group devwhen a PEP 735[dependency-groups] devgroup is declared (whatuv add --devwrites). A project that is not built, asuv init --no-packagewrites (anduv initdid before uv 0.12), gets its[project]dependencies, the dev extra's and the dev group, after arequires-pythoncheck. A package, such as asrc/layout, therefore needs a[build-system]table.
CI does not detect dev dependencies declared through tool-specific metadata,
such as Poetry's [tool.poetry.group.dev.dependencies]; add a
requirements-dev.txt to have CI install that set.
Dependabot
As generated, .github/dependabot.yml covers GitHub Actions only: a new
repository has no manifest, and a pip entry would fail on every run until one
exists. Once the manifest is committed, add this entry under updates: if the
file has none. It holds the core tools at their current major, since a major
bump needs deliberate adoption, and groups their updates. Use
package-ecosystem: uv rather than pip once uv.lock is committed, so
Dependabot updates the lockfile too.
- package-ecosystem: pip
directory: "/"
schedule:
interval: weekly
cooldown:
default-days: 7
open-pull-requests-limit: 10
ignore:
- dependency-name: ruff
update-types: ["version-update:semver-major"]
- dependency-name: mypy
update-types: ["version-update:semver-major"]
- dependency-name: pytest
update-types: ["version-update:semver-major"]
groups:
dev-dependencies:
patterns:
- ruff
- mypy
- pytest
- pytest-*Worktrees
A worktree needs its own virtual environment: create it inside that worktree
and remove it with the worktree. Never copy .venv/ or tool caches
(.mypy_cache/, .ruff_cache/, .pytest_cache/) into a verification copy.
Sources
- When uv builds a project: uv's "Configuring projects" docs, checked 2026-10-15.
- What
uv initwrites: uv's "Creating projects" docs, checked 2026-10-15. - Which files the pip cache hashes, and that it stops when none exists:
actions/setup-pythonv7.0.0,src/cache-distributions/pip-cache.ts,cache-distributor.tsandconstants.ts, checked 2026-10-21. - Why a
pipentry fails without a manifest: GitHub's Dependabot options reference (package-ecosystem) and dependabot-core'spython/lib/dependabot/python/file_fetcher.rb, checked 2026-10-21.