---
name: local-validation-python
description: "Use before running local validation in this Python repository: `ruff`, `mypy`, `pytest`, or installing dependencies in a worktree. Covers the dependency manifest CI requires, how CI picks which dependency set to install, projects whose dev dependencies CI cannot detect, when to add the Dependabot `pip` entry, and the per-worktree virtual environment rule."
title: local-validation-python
canonical_url: https://skilld.dev/gh/bydradev/gh-repo-bootstrapper/local-validation-python
last_updated: 2026-10-30T03:16:22.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install bydradev/gh-repo-bootstrapper/local-validation-python`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/local-validation-python`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/bydradev/gh-repo-bootstrapper/local-validation-python) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/local-validation-python`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/local-validation-python --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/local-validation-python --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# 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.lock` exists:** `uv sync --locked`, which installs exactly the locked
  versions and fails if `uv.lock` is out of date with `pyproject.toml`; run
  `uv lock` and commit the result when it does. CI names a declared `dev` group
  and `dev` extra explicitly, so a `[tool.uv] default-groups` setting cannot
  leave them out.
- **Otherwise:** `requirements-dev.txt` if present, otherwise
  `requirements.txt`.
- **Otherwise, `pyproject.toml`:** like uv, CI builds the project only when it
  declares a `[build-system]` (or has a `setup.py`, or a `setup.cfg` with
  `[metadata]` or `[options]`), and `[tool.uv] package` overrides that. A
  package installs as `-e .`, or `-e ".[dev]"` when a PEP 621
  `[project.optional-dependencies] dev = [...]` extra is declared, adding
  `--group dev` when a PEP 735 `[dependency-groups] dev` group is declared
  (what `uv add --dev` writes). A project that is not built, as
  `uv init --no-package` writes (and `uv init` did before uv 0.12), gets its
  `[project]` dependencies, the dev extra's and the dev group, after a
  `requires-python` check. A package, such as a `src/` 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.

```yaml
  - 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 init` writes: uv's "Creating projects" docs, checked 2026-10-15.
- Which files the pip cache hashes, and that it stops when none exists:
  `actions/setup-python` v7.0.0, `src/cache-distributions/pip-cache.ts`,
  `cache-distributor.ts` and `constants.ts`, checked 2026-10-21.
- Why a `pip` entry fails without a manifest: GitHub's Dependabot options
  reference (`package-ecosystem`) and dependabot-core's
  `python/lib/dependabot/python/file_fetcher.rb`, checked 2026-10-21.
