Python Engineering Profile
Use this profile only after repository discovery identifies the stack. Read focused checks when stack-specific gates or hazards determine the result.
Workflow
- Discover
pyproject.toml, lockfiles, package layout, environment files, tox or nox configuration, and repository scripts.
- Follow repository-defined commands and pinned tool versions before suggesting defaults.
- Review idiomatic design and material hazards, especially mutable defaults, import cycles, dynamic typing gaps, async cancellation, context-manager cleanup, serialization, timezone handling, and environment drift.
- Select proportionate gates from repository scripts, formatting, linting, static typing, unit and integration tests, package builds, and dependency or vulnerability checks when configured.
- Review compatibility across supported Python versions, packaging metadata, public imports, typing behavior, platform wheels, database drivers, and deprecations.
- Report every missing tool, skipped command, unsupported platform, or unavailable environment as incomplete rather than passing.
Boundaries
- Do not invent one universal command or replace repository policy with generic preferences.
- Do not install, upgrade, publish, deploy, apply, or mutate shared state merely to run a gate.
- Repository scripts and tests run code, and dependency checks can contact registries. Run a gate only when the user asked for checks and trusts the repository. Otherwise, name it as the next safe gate.
- Separate static review, executed checks, build evidence, provider state, and live behavior.
Output
Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.
Return Discovery, Hazards, Commands selected, Results, Compatibility, Missing evidence, and Next safe gate.
Example
Synthetic example; not an observed client result.
Input: A supplied Python 3.12 dependency lock and handler show an async request calling a synchronous network client directly. No commands have run.
Output: warning: the synchronous call can block the event loop. Discovery is limited to the supplied Python 3.12 lock and handler; runtime latency is unmeasured. Review cancellation and the client's thread-safety contract before choosing an async client or offloading work. No validation command has been selected or run because repository gates were not supplied. Compatibility evidence and a cancellation test remain missing. Next inspect those gates and the pinned client behavior.
1---2name: stack-python3description: "Reviews Python changes when typing, async code, packaging, dependencies, or tests need focused checks; follows discovered Python versions and repository commands."4license: MIT5metadata:6 source: https://skillmd.com/skills/jovanipink/stack-python7 author: "Measured Studios"8 version: "0.19.0"9 plugin: "measured-stacks"10 invocation: "implicit"11 provenance: "original"12 risk_class: "read-only"13---1415# Python Engineering Profile1617Use this profile only after repository discovery identifies the stack. Read [focused checks](references/checks.md) when stack-specific gates or hazards determine the result.1819## Workflow20211. Discover `pyproject.toml`, lockfiles, package layout, environment files, tox or nox configuration, and repository scripts.222. Follow repository-defined commands and pinned tool versions before suggesting defaults.233. Review idiomatic design and material hazards, especially mutable defaults, import cycles, dynamic typing gaps, async cancellation, context-manager cleanup, serialization, timezone handling, and environment drift.244. Select proportionate gates from repository scripts, formatting, linting, static typing, unit and integration tests, package builds, and dependency or vulnerability checks when configured.255. Review compatibility across supported Python versions, packaging metadata, public imports, typing behavior, platform wheels, database drivers, and deprecations.266. Report every missing tool, skipped command, unsupported platform, or unavailable environment as incomplete rather than passing.2728## Boundaries2930- Do not invent one universal command or replace repository policy with generic preferences.31- Do not install, upgrade, publish, deploy, apply, or mutate shared state merely to run a gate.32- Repository scripts and tests run code, and dependency checks can contact registries. Run a gate only when the user asked for checks and trusts the repository. Otherwise, name it as the next safe gate.33- Separate static review, executed checks, build evidence, provider state, and live behavior.3435## Output3637Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.3839Return Discovery, Hazards, Commands selected, Results, Compatibility, Missing evidence, and Next safe gate.4041## Example4243Synthetic example; not an observed client result.4445Input: A supplied Python 3.12 dependency lock and handler show an async request calling a synchronous network client directly. No commands have run.4647Output: warning: the synchronous call can block the event loop. Discovery is limited to the supplied Python 3.12 lock and handler; runtime latency is unmeasured. Review cancellation and the client's thread-safety contract before choosing an async client or offloading work. No validation command has been selected or run because repository gates were not supplied. Compatibility evidence and a cancellation test remain missing. Next inspect those gates and the pinned client behavior.