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
Maintains concise repository MEMORY.md notes for gotchas, stale memory corrections, and durable user preferences. Use at the start of repository conversations, when the user mentions MEMORY.md, when an error should be remembered to avoid repeating it, or when MEMORY.md content may be wrong.
testing
Use only when the user explicitly names the work-log-writer skill; never auto-activate from generic work log, daily log, EOD summary, status update, or date-range summary requests.
development
Use when implementing non-trivial code changes that should follow TDD (write a failing test first, make the smallest passing change, then refactor safely).
tools
Use when designing, implementing, reviewing, or debugging Codex CLI hooks, including `hooks.json`, `.codex/hooks.json`, feature-flag setup, matcher behavior, event-specific stdin/stdout payloads, and hook scripts for `SessionStart`, `PreToolUse`, `PostToolUse`, `UserPromptSubmit`, or `Stop`.