skills/python-quality-tooling/SKILL.md
Use when configuring or running Python quality tools (ruff, ty, pytest, coverage, CI gates) and when enforcing a pre-merge quality checklist.
npx skillsauth add narumiruna/agent-skills python-quality-toolingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use ruff, ty, pytest, coverage, and prek consistently. Core principle: prefer the repository's single quality gate; otherwise run each tool through uv run.
prek run -a and individual uv run commands.prek run -a as the primary pre-merge gate.uv run.uv add --dev, not as runtime dependencies.| Task | Command |
| --- | --- |
| Lint | uv run ruff check |
| Auto-fix | uv run ruff check --fix |
| Format | uv run ruff format |
| Type check | uv run ty check |
| Test | uv run pytest |
| Coverage | uv run pytest --cov=src --cov-report=term-missing |
| Full repo gate (prek) | prek run -a |
| Install git hooks (prek) | prek install |
Use this order:
prek run -a when the repo uses prek.uv run ruff ..., uv run ty check, and uv run pytest ... commands.Pytest tests MUST be function-based (no class-based tests or unittest.TestCase).
Pre-merge gate:
prek run -a
Fallback when no aggregate gate exists:
uv run ruff check --fix
uv run ruff format
uv run ty check
uv run pytest --cov=src --cov-report=term-missing
prek run -a when a repo standardizes on prek.ruff/pytest invocations without uv run.pre-commit and prek commands in the same repo.class Test*) or unittest.TestCase usage.references/quality.md - Full command set, CI example, and prek install/usage notes (prefer uv tool install prek)development
Score or compare one or more agent skills across trigger clarity, workflow actionability, safety boundaries, verification rigor, incremental knowledge value, and leanness. Use only when the user explicitly asks for ratings, numerical quality scores, rubric-based scorecards, or scored comparisons; use creating-agent-skills for unscored reviews or revisions.
development
Assess or improve an existing codebase's architecture when the user asks about module boundaries, coupling, scattered ownership, testability, change locality, deep modules, seams, or behavior-preserving structural refactoring. Use for cross-module design rather than ordinary diff review or a confirmed edge-case bug fix.
development
Perform read-only security audits, vulnerability assessments, or threat-focused reviews of diffs, pull requests, code paths, or explicitly scoped repositories when security is the primary objective or acceptance criterion. Use reviewing-code for ordinary review with baseline security coverage and hardening-code-paths for fixing confirmed findings.
development
Run iterative multi-reviewer panels over a code diff, verify their findings, apply explicitly authorized fixes, and re-review the updated change until it passes or reaches a stopping condition. Use when the user asks for a panel loop, multi-model code-review consensus, or a review-fix-re-review cycle.