package-maintainer

Automate Python package governance for API exposure, dependencies, and PyPI readiness.

Updated Nov 25, 2025

Search Tags:#versioning #python #packaging #quality #package-management #dependency-tree #api-exports

Ready to run

npx skills add https://github.com/NikhilVijayakumar/Yantra --skill package-maintainer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: package-maintainer
Source: https://github.com/NikhilVijayakumar/Yantra/tree/main/.agent/skills/package-maintainer
Command: npx skills add https://github.com/NikhilVijayakumar/Yantra --skill package-maintainer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manages the library's public API surface, dependency tree, and PyPI readiness, ensuring clean exports, stable dependencies, and smooth packaging workflows.

Core Features & Use Cases

Encapsulation: Keep internal implementations private unless clients need access to the public API.
Dependency hygiene: Align dependencies, separate development tooling, and enforce versioning discipline for releases.
Packaging readiness: Validate PyPI readiness, automate version bumps, and prepare release artifacts for distribution.

Quick Start

Audit the library's public API exposure, dependency tree, and packaging readiness to prepare a release.

Frequently Asked Questions about package-maintainer

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

FAQPage Schema

How do I check my Python package's public API surface before a release?▼

To check your Python package's public API surface before a release, audit the library's API exposure to ensure internal implementations remain encapsulated and only intended functions are exported. This validates packaging readiness and enforces clean exports.

What is the best way to automate semantic versioning for a Python library?▼

Automating semantic versioning for a Python library involves using a governance workflow that enforces versioning discipline during release cycles. This approach validates version bumps and aligns dependency hygiene to prepare safe, reproducible release artifacts.

How do I validate PyPI readiness for a Python package?▼

You validate PyPI readiness for a Python package by running a purity audit script that checks packaging metadata, verifies YAML frontmatter, and ensures dependency graphs are stable. This confirms the package is prepared for distribution.

Does dependency hygiene affect semantic versioning in Python packaging?▼

Yes, dependency hygiene directly affects semantic versioning in Python packaging because separating development tooling and aligning dependencies prevents unexpected breaking changes. Enforcing this discipline ensures safe, reproducible packaging workflows during ongoing maintenance.

When do I need to separate development tooling from core dependencies in a Python library?▼

You need to separate development tooling from core dependencies in a Python library during release cycles to maintain packaging readiness. This dependency hygiene practice prevents runtime conflicts and ensures the public API surface remains stable for clients.