python-package-validation

Runs linting, typing, tests, coverage, and docs validation checks on Python packages.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/MLVisions/agentbuilder_py --skill python-package-validation-mlvisions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: python-package-validation
Source: https://github.com/MLVisions/agentbuilder_py/tree/main/.github/skills/python-package-validation
Command: npx skills add https://github.com/MLVisions/agentbuilder_py --skill python-package-validation-mlvisions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It automates the repetitive quality-assurance workflow for Python packages, catching lint errors, failing tests, low coverage, documentation gaps, and inconsistent refactors before code is committed. ## Core Features & Use Cases - Automated Validation Workflow: Runs ruff linting/formatting, pytest test suites, and coverage reports with pytest-cov in a structured sequence. - Conceptual Diff Review: Reviews git diffs for unfinished implementations, dead code, inconsistent patterns between tools and agents, and upstream/downstream impacts. - Docs and Example Checks: Verifies executable docstring examples, README consistency, and regenerated YAML example files via build scripts. - Use Case: After refactoring an agent runtime module, run this Skill to lint the code, execute targeted then full test suites, check coverage of exported functions, review the diff, and produce a concise commit message. ## Quick Start Run the package validation checks on my current changes and report any lint, test, coverage, or documentation issues before I commit.

Frequently Asked Questions about python-package-validation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run linting and tests before committing Python code?▼

Run ruff check and ruff format for style, then execute pytest for tests and pytest --cov for coverage. This Skill sequences these checks, starting with targeted tests via pytest -k before running the full suite.

How to check test coverage for a Python package?▼

Use pytest --cov=<package> --cov-report=term-missing to see per-file and overall coverage percentages. Ensure all exported functions, especially example tools and agents, have tests proving they work correctly.

Why do my tests show retry backoff waiting messages?▼

Retry backoff messages indicate an underlying design issue such as an agent calling a tool multiple times unnecessarily or a tool making redundant API calls. Fix the root logic issue rather than suppressing the messages.

Can I skip failing tests before committing?▼

No, only Ollama-dependent tests may be skipped; all other tests must pass before committing. Skipping tests or using weak expectations masks real issues and is explicitly disallowed.

What should a good commit message include after validation?▼

Keep it concise with one to three bullets summarizing what changed and why, including key refactors. Do not mention tests passing or general state; focus on the substantive changes.