python-library-review

Reviews Python libraries across packaging, testing, security, documentation, and CI/CD quality dimensions.

1|2|Updated Nov 25, 2017
One-click install
npx skills add https://github.com/asarchami/dotfiles --skill python-library-review-asarchami
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: python-library-review
Source: https://github.com/asarchami/dotfiles/tree/main/dot_config/opencode/skills/python/library-review
Command: npx skills add https://github.com/asarchami/dotfiles --skill python-library-review-asarchami

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Evaluating the health and quality of a Python library before adopting it as a dependency or preparing it for a major release is time-consuming and inconsistent without a structured checklist. This Skill provides a systematic review framework covering structure, packaging, code quality, testing, security, documentation, API design, and CI/CD. ## Core Features & Use Cases - Multi-Dimensional Review: Assesses eight quality areas including pyproject.toml packaging, type hints, test coverage, security scanning, and CI/CD pipelines. - Red Flag and Green Flag Detection: Quickly identifies warning signs like missing tests or setup.py-only packaging, and positive signals like active maintenance and high coverage. - Structured Report Template: Produces a standardized review report with an overall rating, category scores, and prioritized recommendations. - Use Case: Before adding a new third-party package to your project, run this review to audit its test coverage, security posture with bandit and pip-audit, and maintenance activity, then receive an actionable quality report. ## Quick Start Ask the AI to review a Python library by cloning its repository and evaluating its structure, tests, security, and packaging against the review checklist.

Frequently Asked Questions about python-library-review

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

FAQPage Schema
How do I review the quality of a Python library before using it?

Review a Python library by checking its pyproject.toml configuration, running pytest with coverage, scanning with bandit for security issues, and verifying documentation and CI/CD setup. This Skill provides a structured checklist and report template covering all eight quality dimensions.

What are red flags when auditing a Python package?

Key red flags include no tests, missing type hints, setup.py-only packaging without pyproject.toml, pinned exact dependency versions, no LICENSE file, and no commits in over a year. Any of these suggests maintenance or quality risks.

How do I check test coverage for a Python package?

Run pytest with the --cov flag targeting the package source directory to measure coverage. Healthy libraries typically exceed 80 percent coverage, while anything below 70 percent indicates testing gaps that need attention.

What security checks should I run on Python dependencies?

Run bandit against the source directory to detect common security issues and pip-audit to check for known vulnerabilities in dependencies. Also verify there are no hardcoded secrets and that user inputs are validated.

When should I use a library review versus a full security audit?

Use this library review for broad quality assessment across structure, tests, docs, and CI/CD when evaluating dependencies or preparing releases. A dedicated security audit goes deeper into vulnerability analysis and is better when security is the sole concern.