python-package

Audit an entire Python package repository for best-practice compliance — systematically scans the codebase for structure, configuration, typing, testing, CI/CD, documentation, and security issues

Review the current Python package for best-practice violations — project structure, pyproject.toml, typing, testing, CI/CD, documentation, versioning, API design, packaging, security, and developer experience

Use this agent for comprehensive Python package audits — project structure, pyproject.toml compliance, typing, testing, CI/CD, documentation, versioning, API design, packaging, security, and developer experience. Handles both targeted file reviews and full repository audits. Examples: <example>Context: User has a Python package and wants it reviewed for best practices. user: "Review my Python package for best practices" assistant: "I'll use the package-reviewer agent to audit the package." <commentary>Package review for best practices touches all 11 principle areas — comprehensive audit needed.</commentary></example> <example>Context: User wants to check their pyproject.toml and CI setup before publishing. user: "Check if my package is ready to publish to PyPI" assistant: "I'll use the package-reviewer agent to check publishing readiness." <commentary>Publishing readiness review covers pyproject.toml, packaging, CI/CD, security, versioning — comprehensive audit.</commentary></example> <example>Context: User wants to modernize a legacy Python package. user: "Audit my package and tell me what needs to be modernized" assistant: "I'll use the package-reviewer agent to perform a modernization audit." <commentary>Modernization audit requires discovering legacy patterns (setup.py, missing types, old CI) and recommending upgrades across all areas.</commentary></example>

This skill should be used when the user is designing a library's public API surface, defining __all__, organizing imports, creating an exception hierarchy, implementing async/sync dual APIs, adding plugin architecture (pluggy, entry points, protocols), applying progressive disclosure, choosing return types, naming methods, or reviewing backward compatibility. Covers __all__, underscore-prefixed modules, exception trees, httpx _BaseClient pattern, pluggy, entry points, Protocols, dependency injection, configuration patterns.

This skill should be used when the user is setting up GitHub Actions, configuring CI/CD pipelines, creating test matrices, enabling trusted publishing with OIDC, automating PyPI releases, adding Dependabot or Renovate, or configuring Sigstore attestations. Covers workflow architecture, lint/type-check/test/build/publish jobs, caching, concurrency, reusable workflows, SLSA provenance.

This skill should be used when the user is adding a CLI to a Python package, choosing between Click, Typer, and argparse, structuring cli.py or a cli/ directory, creating a __main__.py for python -m support, defining console script entry points, handling exit codes, or organizing subcommands. Covers framework selection, CLI module layout, __main__.py delegation pattern, exit code conventions, and subcommand organization.

This skill should be used when the user is configuring Ruff, setting up mypy, adding type hints, choosing between mypy and pyright, writing py.typed markers, modernizing type annotations (PEP 695/649), using TYPE_CHECKING, setting up pre-commit hooks, configuring ruff format, choosing lint rule sets, or reviewing code quality tooling. Covers Ruff rule sets, mypy strict mode, pyright, modern typing patterns, pre-commit configuration, formatting, and complexity thresholds.

This skill should be used when the user is writing a CONTRIBUTING.md, setting up developer onboarding, creating a Makefile or justfile, adding issue templates, adding PR templates, writing a README, creating a CODE_OF_CONDUCT.md, setting up CODEOWNERS, adding .editorconfig, configuring devcontainers, labeling good first issues, or building project community and governance. Covers one-command dev setup, task automation, contributor funnel, and community health files.

1 hook across 1 event