python-codestyle Profiles Reference Calls the Build Profile PEP 621, Then Admits a pyproject.toml With No [project] Table #1947

.agents/skills/python-codestyle/references/profiles.md, the "Project (the build profile)" bullet (carried verbatim into .github/skills downstream), reads as internally inconsistent:

It is a PEP 621 uv project: [project] with dependencies (...), a [build-system], and a committed uv.lock (...). ... A pyproject.toml beside a requirements*.txt is this profile too, installed with pip, whether or not it carries a [project] table.

The bullet first defines the profile as a PEP 621 uv project with a lockfile, then admits a pip-installed pyproject.toml with no [project] table. That case is neither PEP 621 nor uv, so the definition it opens with is not true of every member of the profile.

Copilot raised this in its review of a downstream re-carry PR, where the text cannot be changed because the carry is verbatim. A likely fix is to state the profile by its classifying trait (third-party runtime dependencies, or the repo's deliverable) and give the uv project and the pip-installed pyproject.toml plus requirements*.txt as its two forms, rather than defining it as one of them.

Generated with Claude Code