Generated banner for Python Pypi Package Builder
Generated logo for Python Pypi Package Builder

Python Pypi Package Builder

GitHubOfficialFirst committed by Dhruvpatel004Distributed by GitHub

  • Skill
  • Workflow
  • Software development
  • MIT
  • Low risk
  • Has scripts

From the author

End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI. Covers all four build backends (setuptools+setuptools_scm, hatchling, flit, poetry), PEP 440 versioning, semantic versioning, dynamic git-tag versioning, OOP/SOLID design, type hints (PEP 484/526/544/561), Trusted Publishing (OIDC), and the full PyPA packaging flow. Use for: creating Python packages, pip-installable SDKs, CLI tools, framework plugins, pyproject.toml setup, py.typed, setuptools_scm, semver, mypy, pre-commit, GitHub Actions CI/CD, or PyPI publishing.
— the description by Dhruvpatel004

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides an end-to-end framework for the entire Python packaging lifecycle. It covers selecting build backends (setuptools, hatchling, flit, poetry), configuring project structures, implementing robust versioning strategies, and setting up automated CI/CD pipelines. It emphasizes modern standards including PEP 440, PEP 561 type hints, and Trusted Publishing for secure PyPI releases.

What it does

  • Generates complete project directory layouts with a single command.
  • Configures pyproject.toml for various build backends and dependency management.
  • Implements automated versioning using git tags via setuptools_scm.
  • Sets up GitHub Actions for automated linting, testing, and PyPI publishing.
  • Provides patterns for SOLID design, type hinting, and plugin architectures.
  • Guides the user through the PyPA packaging flow from local build to release.

When to use it

  • When starting a new Python library, SDK, or CLI tool from scratch.
  • When refactoring an existing project to follow modern packaging standards.
  • When you need to set up automated CI/CD and PyPI publishing pipelines.
  • When you need guidance on choosing the right build backend for your project requirements.

Advantages

  • Standardizes project structure and configuration across different libraries.
  • Reduces manual overhead in versioning and release management.
  • Ensures high code quality through integrated linting, typing, and testing.
  • Promotes secure publishing practices using OIDC Trusted Publishing.

Usage examples

“I want to start a new Python SDK project. How should I structure it?”
The agent will guide you through selecting the src/ layout, choosing a build backend, and using the scaffold script to generate the initial files.
“How do I set up my Python library to publish to PyPI automatically?”
The agent will provide the necessary GitHub Actions configuration for Trusted Publishing and explain the required git-tagging release workflow.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/github/python-pypi-package-builder/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip python-pypi-package-builder.zip -d .agents/skills

Documentation by Dhruvpatel004

Python PyPI Package Builder Skill

A complete, battle-tested guide for building, testing, linting, versioning, typing, and publishing a production-grade Python library to PyPI — from first commit to community-ready release.

AI Agent Instruction: Read this entire file before writing a single line of code or creating any file. Every decision — layout, backend, versioning strategy, patterns, CI — has a decision rule here. Follow the decision trees in order. This skill applies to any Python package type (utility, SDK, CLI, plugin, data library). Do not skip sections.


Quick Navigation

Section in this fileWhat it covers
1. Skill TriggerWhen to load this skill
2. Package Type DecisionIdentify what you are building
3. Folder Structure Decisionsrc/ vs flat vs monorepo
4. Build Backend Decisionsetuptools / hatchling / flit / poetry
5. PyPA Packaging FlowThe canonical publish pipeline
6. Project Structure TemplatesFull layouts for every option
7. Versioning StrategyPEP 440, semver, dynamic vs static
Reference fileWhat it covers
references/pyproject-toml.mdAll four backend templates, setuptools_scm, py.typed, tool configs
references/library-patterns.mdOOP/SOLID, type hints, core class design, factory, protocols, CLI
references/testing-quality.mdconftest.py, unit/backend/async tests, ruff/mypy/pre-commit
references/ci-publishing.mdci.yml, publish.yml, Trusted Publishing, TestPyPI, CHANGELOG, release checklist
references/community-docs.mdREADME, docstrings, CONTRIBUTING, SECURITY, anti-patterns, master checklist
references/architecture-patterns.mdBackend system (plugin/strategy), config layer, transport layer, CLI, backend injection
references/versioning-strategy.mdPEP 440, SemVer, pre-release, setuptools_scm deep-dive, flit static, decision engine
references/release-governance.mdBranch strategy, branch protection, OIDC, tag author validation, prevent invalid tags
references/tooling-ruff.mdRuff-only setup (replaces black/isort), mypy config, pre-commit, asyncio_mode=auto

Scaffold script: run python skills/python-pypi-package-builder/scripts/scaffold.py --name your-package-name to generate the entire directory layout, stub files, and pyproject.toml in one command.


1. Skill Trigger

Load this skill whenever the user wants to:

  • Create, scaffold, or publish a Python package or library to PyPI

  • Build a pip-installable SDK, utility, CLI tool, or framework extension

  • Set up pyproject.toml, linting, mypy, pre-commit, or GitHub Actions for a Python project

  • Understand versioning (setuptools_scm, PEP 440, semver, static versioning)

  • Understand PyPA specs: py.typed, MANIFEST.in, RECORD, classifiers

  • Publish to PyPI using Trusted Publishing (OIDC) or API tokens

  • Refactor an existing package to follow modern Python packaging standards

  • Add type hints, protocols, ABCs, or dataclasses to a Python library

  • Apply OOP/SOLID design patterns to a Python package

  • Choose between build backends (setuptools, hatchling, flit, poetry)

Also trigger for phrases like: "build a Python SDK", "publish my library", "set up PyPI CI", "create a pip package", "how do I publish to PyPI", "pyproject.toml help", "PEP 561 typed", "setuptools_scm version", "semver Python", "PEP 440", "git tag release", "Trusted Publishing".


2. Package Type Decision

Identify what the user is building before writing any code. Each type has distinct patterns.

Decision Table
TypeCore PatternEntry PointKey DepsExample Packages
Utility libraryModule of pure functions + helpersImport API onlyMinimalarrow, humanize, boltons, more-itertools
API client / SDKClass with methods, auth, retry logicImport API onlyhttpx or requestsboto3, stripe-python, openai
CLI toolCommand functions + argument parser[project.scripts] or [project.entry-points]click or typerblack, ruff, httpie, rich
Framework pluginPlugin class, hook registration[project.entry-points."framework.plugin"]Framework deppytest-*, django-*, flask-*
Data processing libraryClasses + functional pipelineImport API onlyOptional: numpy, pandaspydantic, marshmallow, cerberus
Mixed / genericCombination of aboveVariesVariesMany real-world packages

Decision Rule: Ask the user if unclear. A package can combine types (e.g., SDK with a CLI entry point) — use the primary type for structural decisions and add secondary type patterns on top.

For implementation patterns of each type, see references/library-patterns.md.

Package Naming Rules
  • PyPI name: all lowercase, hyphens — my-python-library

  • Python import name: underscores — my_python_library

  • Check availability: https://pypi.org/search/ before starting

  • Avoid shadowing popular packages (verify pip install <name> fails first)


3. Folder Structure Decision

Decision Tree
Does the package have 5+ internal modules OR multiple contributors OR complex sub-packages?
├── YES → Use src/ layout
│         Reason: prevents accidental import of uninstalled code during development;
│         separates source from project root files; PyPA-recommended for large projects.
│
├── NO → Is it a single-module, focused package (e.g., one file + helpers)?
│         ├── YES → Use flat layout
│         └── NO (medium complexity) → Use flat layout, migrate to src/ if it grows
│
└── Is it multiple related packages under one namespace (e.g., myorg.http, myorg.db)?
          └── YES → Use namespace/monorepo layout
Quick Rule Summary
SituationUse
New project, unknown future sizesrc/ layout (safest default)
Single-purpose, 1–4 modulesFlat layout
Large library, many contributorssrc/ layout
Multiple packages in one repoNamespace / monorepo
Migrating old flat projectKeep flat; migrate to src/ at next major version

4. Build Backend Decision

Decision Tree
Does the user need version derived automatically from git tags?
├── YES → Use setuptools + setuptools_scm
│         (git tag v1.0.0 → that IS your release workflow)
│
└── NO → Does the user want an all-in-one tool (deps + build + publish)?
          ├── YES → Use poetry (v2+ supports standard [project] table)
          │
          └── NO → Is the package pure Python with no C extensions?
                    ├── YES, minimal config preferred → Use flit
                    │   (zero config, auto-discovers version from __version__)
                    │
                    └── YES, modern & fast preferred → Use hatchling
                        (zero-config, plugin system, no setup.py needed)

Does the package have C/Cython/Fortran extensions?
└── YES → MUST use setuptools (only backend with full native extension support)
Backend Comparison
BackendVersion sourceConfigC extensionsBest for
setuptools + setuptools_scmgit tags (automatic)pyproject.toml + optional setup.py shimYesProjects with git-tag releases; any complexity
hatchlingmanual or pluginpyproject.toml onlyNoNew pure-Python projects; fast, modern
flit__version__ in __init__.pypyproject.toml onlyNoVery simple, single-module packages
poetrypyproject.toml fieldpyproject.toml onlyNoTeams wanting integrated dep management

For all four complete pyproject.toml templates, see references/pyproject-toml.md.


5. PyPA Packaging Flow

This is the canonical end-to-end flow from source code to user install. Every step must be understood before publishing.

1. SOURCE TREE
   Your code in version control (git)
   └── pyproject.toml describes metadata + build system

2. BUILD
   python -m build
   └── Produces two artifacts in dist/:
       ├── *.tar.gz   → source distribution (sdist)
       └── *.whl      → built distribution (wheel) — preferred by pip

3. VALIDATE
   twine check dist/*
   └── Checks metadata, README rendering, and PyPI compatibility

4. TEST PUBLISH (first release only)
   twine upload --repository testpypi dist/*
   └── Verify: pip install --index-url https://test.pypi.org/simple/ your-package

5. PUBLISH
   twine upload dist/*          ← manual fallback
   OR GitHub Actions publish.yml  ← recommended (Trusted Publishing / OIDC)

6. USER INSTALL
   pip install your-package
   pip install "your-package[extra]"
Key PyPA Concepts
ConceptWhat it means
sdistSource distribution — your source + metadata; used when no wheel is available
wheel (.whl)Pre-built binary — pip extracts directly into site-packages; no build step
PEP 517/518Standard build system interface via pyproject.toml [build-system] table
PEP 621Standard [project] table in pyproject.toml; all modern backends support it
PEP 639license key as SPDX string (e.g., "MIT", "Apache-2.0") — not {text = "MIT"}
PEP 561py.typed empty marker file — tells mypy/IDEs this package ships type information

For complete CI workflow and publishing setup, see references/ci-publishing.md.


6. Project Structure Templates

your-package/
├── src/
│   └── your_package/
│       ├── __init__.py           # Public API: __all__, __version__
│       ├── py.typed              # PEP 561 marker — EMPTY FILE
│       ├── core.py               # Primary implementation
│       ├── client.py             # (API client type) or remove
│       ├── cli.py                # (CLI type) click/typer commands, or remove
│       ├── config.py             # Settings / configuration dataclass
│       ├── exceptions.py         # Custom exception hierarchy
│       ├── models.py             # Data classes, Pydantic models, TypedDicts
│       ├── utils.py              # Internal helpers (prefix _utils if private)
│       ├── types.py              # Shared type aliases and TypeVars
│       └── backends/             # (Plugin pattern) — remove if not needed
│           ├── __init__.py       # Protocol / ABC interface definition
│           ├── memory.py         # Default zero-dep implementation
│           └── redis.py          # Optional heavy implementation
├── tests/
│   ├── __init__.py
│   ├── conftest.py               # Shared fixtures
│   ├── unit/
│   │   ├── __init__.py
│   │   ├── test_core.py
│   │   ├── test_config.py
│   │   └── test_models.py
│   ├── integration/
│   │   ├── __init__.py
│   │   └── test_backends.py
│   └── e2e/                      # Optional: end-to-end tests
│       └── __init__.py
├── docs/                         # Optional: mkdocs or sphinx
├── scripts/
│   └── scaffold.py
├── .github/
│   ├── workflows/
│   │   ├── ci.yml
│   │   └── publish.yml
│   └── ISSUE_TEMPLATE/
│       ├── bug_report.md
│       └── feature_request.md
├── .pre-commit-config.yaml
├── pyproject.toml
├── CHANGELOG.md
├── CONTRIBUTING.md
├── SECURITY.md
├── LICENSE
├── README.md
└── .gitignore
B. Flat Layout (Small / focused packages)
your-package/
├── your_package/         # ← at root, not inside src/
│   ├── __init__.py
│   ├── py.typed
│   └── ... (same internal structure)
├── tests/
└── ... (same top-level files)
your-org/
├── packages/
│   ├── your-org-core/
│   │   ├── src/your_org/core/
│   │   └── pyproject.toml
│   ├── your-org-http/
│   │   ├── src/your_org/http/
│   │   └── pyproject.toml
│   └── your-org-cli/
│       ├── src/your_org/cli/
│       └── pyproject.toml
├── .github/workflows/
└── README.md

Each sub-package has its own pyproject.toml. They share the your_org namespace via PEP 420 implicit namespace packages (no __init__.py in the namespace root).

Internal Module Guidelines
FilePurposeWhen to include
__init__.pyPublic API surface; re-exports; __version__Always
py.typedPEP 561 typed-package marker (empty)Always
core.pyPrimary class / main logicAlways
config.pySettings dataclass or Pydantic modelWhen configurable
exceptions.pyException hierarchy (YourBaseError → specifics)Always
models.pyData models / DTOs / TypedDictsWhen data-heavy
utils.pyInternal helpers (not part of public API)As needed
types.pyShared TypeVar, TypeAlias, Protocol definitionsWhen complex typing
cli.pyCLI entry points (click/typer)CLI type only
backends/Plugin/strategy patternWhen swappable implementations
_compat.pyPython version compatibility shimsWhen 3.9–3.13 compat needed

7. Versioning Strategy

PEP 440 — The Standard
Canonical form:  N[.N]+[{a|b|rc}N][.postN][.devN]

Examples:
  1.0.0          Stable release
  1.0.0a1        Alpha (pre-release)
  1.0.0b2        Beta
  1.0.0rc1       Release candidate
  1.0.0.post1    Post-release (e.g., packaging fix only)
  1.0.0.dev1     Development snapshot (not for PyPI)
MAJOR.MINOR.PATCH

MAJOR: Breaking API change (remove/rename public function/class/arg)
MINOR: New feature, fully backward-compatible
PATCH: Bug fix, no API change
# How it works:
git tag v1.0.0          →  installed version = 1.0.0
git tag v1.1.0          →  installed version = 1.1.0
(commits after tag)     →  version = 1.1.0.post1  (suffix stripped for PyPI)

# In code — NEVER hardcode when using setuptools_scm:
from importlib.metadata import version, PackageNotFoundError
try:
    __version__ = version("your-package")
except PackageNotFoundError:
    __version__ = "0.0.0-dev"    # Fallback for uninstalled dev checkouts

Required pyproject.toml config:

[tool.setuptools_scm]
version_scheme = "post-release"
local_scheme   = "no-local-version"   # Prevents +g<hash> from breaking PyPI uploads

Critical: always set fetch-depth: 0 in every CI checkout step. Without full git history, setuptools_scm cannot find tags and the build version silently falls back to 0.0.0+dev.

Static versioning (flit, hatchling manual, poetry)
# your_package/__init__.py
__version__ = "1.0.0"    # Update this before every release
Version specifier best practices for dependencies
# In [project] dependencies:
"httpx>=0.24"            # Minimum version — PREFERRED for libraries
"httpx>=0.24,<1.0"       # Upper bound only when a known breaking change exists
"httpx==0.27.0"          # Pin exactly ONLY in applications, NOT libraries

# NEVER do this in a library — it breaks dependency resolution for users:
# "httpx~=0.24.0"        # Too tight
# "httpx==0.27.*"        # Fragile
Version bump → release flow
# 1. Update CHANGELOG.md — move [Unreleased] entries to [x.y.z] - YYYY-MM-DD
# 2. Commit the changelog
git add CHANGELOG.md
git commit -m "chore: prepare release vX.Y.Z"
# 3. Tag and push — this triggers publish.yml automatically
git tag vX.Y.Z
git push origin main --tags
# 4. Monitor GitHub Actions → verify on https://pypi.org/project/your-package/

For complete pyproject.toml templates for all four backends, see references/pyproject-toml.md.


Where to Go Next

After understanding decisions and structure:

  1. Set up pyproject.toml → references/pyproject-toml.md All four backend templates (setuptools+scm, hatchling, flit, poetry), full tool configs, py.typed setup, versioning config.

  2. Write your library code → references/library-patterns.md OOP/SOLID principles, type hints (PEP 484/526/544/561), core class design, factory functions, __init__.py, plugin/backend pattern, CLI entry point.

  3. Add tests and code quality → references/testing-quality.md conftest.py, unit/backend/async tests, parametrize, ruff/mypy/pre-commit setup.

  4. Set up CI/CD and publish → references/ci-publishing.md ci.yml, publish.yml with Trusted Publishing (OIDC, no API tokens), CHANGELOG format, release checklist.

  5. Polish for community/OSS → references/community-docs.md README sections, docstring format, CONTRIBUTING, SECURITY, issue templates, anti-patterns table, and master release checklist.

  6. Design backends, config, transport, CLI → references/architecture-patterns.md Backend system (plugin/strategy pattern), Settings dataclass, HTTP transport layer, CLI with click/typer, backend injection rules.

  7. Choose and implement a versioning strategy → references/versioning-strategy.md PEP 440 canonical forms, SemVer rules, pre-release identifiers, setuptools_scm deep-dive, flit static versioning, decision engine (DEFAULT/BEGINNER/MINIMAL).

  8. Govern releases and secure the publish pipeline → references/release-governance.md Branch strategy, branch protection rules, OIDC Trusted Publishing setup, tag author validation in CI, tag format enforcement, full governed publish.yml.

  9. Simplify tooling with Ruff → references/tooling-ruff.md Ruff-only setup replacing black/isort/flake8, mypy config, pre-commit hooks, asyncio_mode=auto (remove @pytest.mark.asyncio), migration guide.

Files

references/community-docs.md

Community Docs, PR Checklist, Anti-patterns, and Release Checklist

Table of Contents

  1. README.md required sections

  2. Docstrings — Google style

  3. CONTRIBUTING.md template

  4. SECURITY.md template

  5. GitHub Issue Templates

  6. PR Checklist

  7. Anti-patterns to avoid

  8. Master Release Checklist


1. README.md Required Sections

A good README is the single most important file for adoption. Users decide in 30 seconds whether to use your library based on the README.

# your-package

> One-line description — what it does and why it's useful.

[![PyPI version](https://badge.fury.io/py/your-package.svg)](https://pypi.org/project/your-package/)
[![Python Versions](https://img.shields.io/pypi/pyversions/your-package)](https://pypi.org/project/your-package/)
[![CI](https://github.com/you/your-package/actions/workflows/ci.yml/badge.svg)](https://github.com/you/your-package/actions/workflows/ci.yml)
[![Coverage](https://codecov.io/gh/you/your-package/branch/master/graph/badge.svg)](https://codecov.io/gh/you/your-package)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)

## Installation

pip install your-package

# With Redis backend:
pip install "your-package[redis]"

## Quick Start

(A copy-paste working example — no setup required to run it)

from your_package import YourClient

client = YourClient(api_key="sk-...")
result = client.process({"input": "value"})
print(result)

## Features

- Feature 1
- Feature 2

## Configuration

| Parameter | Type | Default | Description |
|---|---|---|—--|
| api_key | str | required | Authentication credential |
| timeout | int | 30 | Request timeout in seconds |
| retries | int | 3 | Number of retry attempts |

## Backends

Brief comparison — in-memory vs Redis — and when to use each.

## Contributing

See [CONTRIBUTING.md](./CONTRIBUTING.md)

## Changelog

See [CHANGELOG.md](./CHANGELOG.md)

## License

MIT — see [LICENSE](./LICENSE)

2. Docstrings — Google Style

Use Google-style docstrings for every public class, method, and function. IDEs display these as tooltips, mkdocs/sphinx can auto-generate documentation from them, and they convey intent clearly to contributors.

class YourClient:
    """
    Main client for <purpose>.

    Args:
        api_key: Authentication credential.
        timeout: Request timeout in seconds. Defaults to 30.
        retries: Number of retry attempts. Defaults to 3.

    Raises:
        ValueError: If api_key is empty or timeout is non-positive.

    Example:
        >>> from your_package import YourClient
        >>> client = YourClient(api_key="sk-...")
        >>> result = client.process({"input": "value"})
    """

3. CONTRIBUTING.md

# Contributing to your-package

## Development Setup

git clone https://github.com/you/your-package
cd your-package
pip install -e ".[dev]"
pre-commit install

## Running Tests

pytest

## Running Linting

ruff check .
black . --check
mypy your_package/

## Submitting a PR

1. Fork the repository
2. Create a feature branch: `git checkout -b feat/your-feature`
3. Make changes with tests
4. Ensure CI passes: `pre-commit run --all-files && pytest`
5. Update `CHANGELOG.md` under `[Unreleased]`
6. Open a PR — use the PR template

## Commit Message Format (Conventional Commits)

- `feat: add Redis backend`
- `fix: correct retry behavior on timeout`
- `docs: update README quick start`
- `chore: bump ruff to 0.5`
- `test: add edge cases for memory backend`

## Reporting Bugs

Use the GitHub issue template. Include Python version, package version,
and a minimal reproducible example.

4. SECURITY.md

# Security Policy

## Supported Versions

| Version | Supported |
|---|---|
| 1.x.x   | Yes       |
| < 1.0   | No        |

## Reporting a Vulnerability

Do NOT open a public GitHub issue for security vulnerabilities.

Report via: GitHub private security reporting (preferred)
or email: [email protected]

Include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)

We aim to acknowledge within 48 hours and resolve within 14 days.

5. GitHub Issue Templates

.github/ISSUE_TEMPLATE/bug_report.md
---
name: Bug Report
about: Report a reproducible bug
labels: bug
---

**Python version:**
**Package version:**

**Describe the bug:**

**Minimal reproducible example:**
```python
# paste code here

Expected behavior:

Actual behavior:


### `.github/ISSUE_TEMPLATE/feature_request.md`

```markdown
---
name: Feature Request
about: Suggest a new feature or enhancement
labels: enhancement
---

**Problem this would solve:**

**Proposed solution:**

**Alternatives considered:**

6. PR Checklist

All items must be checked before requesting review. CI must be fully green.

Code Quality Gates
[ ] ruff check . — zero errors
[ ] black . --check — zero formatting issues
[ ] isort . --check-only — imports sorted correctly
[ ] mypy your_package/ — zero type errors
[ ] pytest — all tests pass
[ ] Coverage >= 80% (enforced by fail_under in pyproject.toml)
[ ] All GitHub Actions workflows green
Structure
[ ] pyproject.toml: name, dynamic/version, description, requires-python, license, authors,
    keywords (10+), classifiers, dependencies, all [project.urls] filled in
[ ] dynamic = ["version"] if using setuptools_scm
[ ] [tool.setuptools_scm] with local_scheme = "no-local-version"
[ ] setup.py shim present (if using setuptools_scm)
[ ] py.typed marker file exists in the package directory (empty file)
[ ] py.typed listed in [tool.setuptools.package-data]
[ ] "Typing :: Typed" classifier in pyproject.toml
[ ] __init__.py has __all__ listing all public symbols
[ ] __version__ via importlib.metadata (not hardcoded string)
Testing
[ ] conftest.py has shared fixtures for client and backend
[ ] Core happy path tested
[ ] Error conditions and edge cases tested
[ ] Each backend tested independently in isolation
[ ] Redis backend tested in separate CI job with redis service (if applicable)
[ ] asyncio_mode = "auto" in pyproject.toml (for async tests)
[ ] fetch-depth: 0 in all CI checkout steps
Optional Backend (if applicable)
[ ] BaseBackend abstract class defines the interface
[ ] MemoryBackend works with zero extra deps
[ ] RedisBackend raises ImportError with clear pip install hint if redis not installed
[ ] Both backends unit-tested independently
[ ] redis extra declared in [project.optional-dependencies]
[ ] README shows both install paths (base and [redis])
Changelog & Docs
[ ] CHANGELOG.md updated under [Unreleased]
[ ] README has: description, install, quick start, config table, badges, license
[ ] All public symbols have Google-style docstrings
[ ] CONTRIBUTING.md: dev setup, test/lint commands, PR instructions
[ ] SECURITY.md: supported versions, reporting process
[ ] .github/ISSUE_TEMPLATE/bug_report.md
[ ] .github/ISSUE_TEMPLATE/feature_request.md
CI/CD
[ ] ci.yml: lint + mypy + test matrix (all supported Python versions)
[ ] ci.yml: separate job for Redis backend with redis service
[ ] publish.yml: triggered on v*.*.* tags, uses Trusted Publishing (OIDC)
[ ] fetch-depth: 0 in all workflow checkout steps
[ ] pypi environment created in GitHub repo Settings → Environments
[ ] No API tokens in repository secrets

7. Anti-patterns to Avoid

Anti-patternWhy it's badCorrect approach
__version__ = "1.0.0" hardcoded with setuptools_scmGoes stale after first git tagUse importlib.metadata.version()
Missing fetch-depth: 0 in CI checkoutsetuptools_scm can't find tags → version = 0.0.0+devAdd fetch-depth: 0 to every checkout step
local_scheme not set+g<hash> suffix breaks PyPI uploads (local versions rejected)local_scheme = "no-local-version"
Missing py.typed fileIDEs and mypy don't see package as typedCreate empty py.typed in package root
py.typed not in package-dataFile missing from installed wheel — uselessAdd to [tool.setuptools.package-data]
Importing optional dep at module topImportError on import your_package for all usersLazy import inside the function/class that needs it
Duplicating metadata in setup.pyConflicts with pyproject.toml; driftsKeep setup.py as 3-line shim only
No fail_under in coverage configCoverage regressions go unnoticedSet fail_under = 80
No mypy in CIType errors silently accumulateAdd mypy step to ci.yml
API tokens in GitHub Secrets for PyPISecurity risk, rotation burdenUse Trusted Publishing (OIDC)
Committing directly to main/masterBypasses CI checksEnforce via no-commit-to-branch pre-commit hook
Missing [Unreleased] section in CHANGELOGChanges pile up and get forgotten at release timeKeep [Unreleased] updated every PR
Pinning exact dep versions in a libraryBreaks dependency resolution for usersUse >= lower bounds only; avoid ==
No __all__ in __init__.pyUsers can accidentally import internal helpersDeclare __all__ with every public symbol
from your_package import * in testsTests pass even when imports are brokenAlways use explicit imports
No SECURITY.mdNo path for responsible vulnerability disclosureAdd file with response timeline
Any everywhere in type hintsDefeats mypy entirelyUse object for truly arbitrary values
Union return typesForces every caller to write isinstance() checksReturn concrete types; use overloads
setup.cfg + pyproject.toml both activeConflicts and confusing for contributorsMigrate everything to pyproject.toml
Releasing on untagged commitsVersion number is meaninglessAlways tag before release
Not testing on all supported Python versionsBreakage discovered by users, not youMatrix test in CI
license = {text = "MIT"} (old form)Deprecated; PEP 639 uses SPDX stringslicense = "MIT"
No issue templatesBug reports are inconsistentAdd bug_report.md + feature_request.md

8. Master Release Checklist

Run through every item before pushing a release tag. CI must be fully green.

Code Quality
[ ] ruff check . — zero errors
[ ] ruff format . --check — zero formatting issues
[ ] mypy src/your_package/ — zero type errors
[ ] pytest — all tests pass
[ ] Coverage >= 80% (fail_under enforced in pyproject.toml)
[ ] All GitHub Actions CI jobs green (lint + test matrix)
Project Structure
[ ] pyproject.toml — name, description, requires-python, license (SPDX string), authors,
    keywords (10+), classifiers (Python versions + Typing :: Typed), urls (all 5 fields)
[ ] dynamic = ["version"] set (if using setuptools_scm or hatch-vcs)
[ ] [tool.setuptools_scm] with local_scheme = "no-local-version"
[ ] setup.py shim present (if using setuptools_scm)
[ ] py.typed marker file exists (empty file in package root)
[ ] py.typed listed in [tool.setuptools.package-data]
[ ] "Typing :: Typed" classifier in pyproject.toml
[ ] __init__.py has __all__ listing all public symbols
[ ] __version__ reads from importlib.metadata (not hardcoded)
Testing
[ ] conftest.py has shared fixtures for client and backend
[ ] Core happy path tested
[ ] Error conditions and edge cases tested
[ ] Each backend tested independently in isolation
[ ] asyncio_mode = "auto" in pyproject.toml (for async tests)
[ ] fetch-depth: 0 in all CI checkout steps
CHANGELOG and Docs
[ ] CHANGELOG.md: [Unreleased] entries moved to [x.y.z] - YYYY-MM-DD
[ ] README has: description, install commands, quick start, config table, badges
[ ] All public symbols have Google-style docstrings
[ ] CONTRIBUTING.md: dev setup, test/lint commands, PR instructions
[ ] SECURITY.md: supported versions, reporting process with timeline
Versioning
[ ] All CI checks pass on the commit you plan to tag
[ ] CHANGELOG.md updated and committed
[ ] Git tag follows format v1.2.3 (semver, v prefix)
[ ] No stale local_scheme suffixes will appear in the built wheel name
CI/CD
[ ] ci.yml: lint + mypy + test matrix (all supported Python versions)
[ ] publish.yml: triggered on v*.*.* tags, uses Trusted Publishing (OIDC)
[ ] pypi environment created in GitHub repo Settings → Environments
[ ] No API tokens stored in repository secrets
The Release Command Sequence
# 1. Run full local validation
ruff check . ; ruff format . --check ; mypy src/your_package/ ; pytest

# 2. Update CHANGELOG.md — move [Unreleased] to [x.y.z]
# 3. Commit the changelog
git add CHANGELOG.md
git commit -m "chore: prepare release vX.Y.Z"

# 4. Tag and push — this triggers publish.yml automatically
git tag vX.Y.Z
git push origin main --tags

# 5. Monitor: https://github.com/<you>/<pkg>/actions
# 6. Verify: https://pypi.org/project/your-package/

Requirements and compatibility

Written for: GitHub Copilot

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs a command-line tool, Needs Python

Security

What our scanner noticed· Low risk

  • Instructions that use the network
  • Scripts that your agent may run

This skill includes scripts that your agent may run. Read them before you use it.

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

First committed by
GitHub avatar of Dhruvpatel004Dhruvpatel004
Publisher
GitHub (Official)
Distributed by
GitHub
Source
github/awesome-copilot · skills/python-pypi-package-builder · commit 797337f
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Contributors
Dhruvpatel004

AutoGineer is not affiliated with or endorsed by Dhruvpatel004 or GitHub.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download python-pypi-package-builder.zip