reviewing-python-libraries
Comprehensively reviews Python libraries for quality across project structure, packaging, code quality, testing, security, documentation, API design, and CI/CD. Provides actionable feedback and improvement recommendations. Use when evaluating library health, preparing for major releases, or auditing dependencies.
Works with
--- name: reviewing-python-libraries description: Comprehensively reviews Python libraries for quality across project structure, packaging, code quality, testing, security, documentation, API design, and CI/CD. Provides actionable feedback and improvement recommendations. Use when evaluating library health, preparing for major releases, or auditing dependencies. license: MIT --- # Python Library Review ## Quick Health Check (5 min) ```bash git clone https://github.com/user/package && cd package head -50 pyproject.toml # Modern config? ls tests/ && uv run pytest --collect-only # Tests exist? uv run pytest --cov=package | tail -20 # Coverage? uvx bandit -r src/ # Security? ``` ## Review Dimensions | Area | Check For | |------|-----------| | Structure | src/ layout, py.typed marker | | Packaging | pyproject.toml (not setup.py) | | Code | Type hints, docstrings, no anti-patterns | | Tests | 80%+ coverage, edge cases | | Security | No secrets, input validation, pip-audit clean | | Docs | README, API docs, changelog | | API | Consistent naming, sensible defaults | | CI/CD | Tests on PR, multi-Python, security scans | ## Red Flags 🚩 - No tests - No type hints - setup.py only (no pyproject.toml) - Pinned exact versions for all deps - No LICENSE file - Last commit > 1 year ago ## Green Flags ✅ - Active maintenance (recent commits) - High test coverage (>85%) - Comprehensive CI/CD - Type hints throughout - Clear documentation - Semantic versioning ## Report Template ```markdown # Library Review: [package] **Rating:** [Excellent/Good/Needs Work/Significant Issues] ## Strengths - [Strength 1] ## Areas for Improvement - [Issue 1] - Severity: High/Medium/Low ## Category Scores | Category | Score | |----------|-------| | Structure | ⭐⭐⭐⭐⭐ | | Testing | ⭐⭐⭐☆☆ | | Security | ⭐⭐⭐⭐☆ | ## Recommendations 1. [High priority action] 2. [Medium priority action] ``` For detailed checklists, see: - **[CHECKLIST.md](CHECKLIST.md)** - Full review checklist - **[REPORT_TEMPLATE.md](REPORT_TEMPLATE.md)** - Complete report template ## Best Practices Checklist ``` Essential: - [ ] pyproject.toml valid - [ ] Tests exist and pass - [ ] README has install/usage - [ ] LICENSE present - [ ] No hardcoded secrets Important: - [ ] Type hints on public API - [ ] CI runs tests on PRs - [ ] Coverage > 85% - [ ] Changelog maintained Recommended: - [ ] src/ layout - [ ] py.typed marker - [ ] Security scanning in CI - [ ] Contributing guide ``` ## Learn More This skill is based on the [Guide to Developing High-Quality Python Libraries](https://mcginniscommawill.com/guides/python-library-development/) by [Will McGinnis](https://mcginniscommawill.com/). The review criteria in this skill draw from all posts in the guide — see the [full guide](https://mcginniscommawill.com/guides/python-library-development/) for detailed quality criteria across every dimension of library development.
More Testing skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
setup-pre-commit
mattpocock/skills
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

