tox-config

Generate standardized tox.ini files for Python, C++ extension, and docs-only projects.

3|Updated Feb 5, 2026

Search Tags:#automation #ci/cd #development workflow #configuration #tox #python packaging

Ready to run

npx skills add https://github.com/Sun-Lab-NBB/ataraxis --skill tox-config

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tox-config
Source: https://github.com/Sun-Lab-NBB/ataraxis/tree/main/plugins/automation/skills/tox-config
Command: npx skills add https://github.com/Sun-Lab-NBB/ataraxis --skill tox-config

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that all tox.ini files across Sun Lab projects adhere to a consistent, optimized, and maintainable standard, streamlining development automation and toolchain integration.

Core Features & Use Cases

Standardized Configuration: Enforces Sun Lab's conventions for tox.ini structure, environment definitions, and toolchain usage (mamba, uv, tox).
Project Archetype Support: Provides specific guidance for different project types (Full Python, C++ extension, Reduced Python, C++ docs-only).
Use Case: When creating a new Python library for the Ataraxis framework, use this Skill to generate a compliant tox.ini that includes environments for linting, testing across multiple Python versions, building, and documentation.

Quick Start

Use the tox-config skill to create a new tox.ini file for a full Python project.

Frequently Asked Questions about tox-config

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

FAQPage Schema

How do I standardize tox.ini for Python packaging and CI/CD automation?▼

To standardize tox.ini for Python packaging, apply predefined conventions for envlist patterns, environment definitions, and dependency installation strategies. This ensures consistent development automation pipelines across different project archetypes.

What is the best way to configure tox with mamba and uv toolchains?▼

Configuring tox with mamba and uv toolchains involves managing environment definitions and dependency installation strategies to integrate the package managers. This standardizes the toolchain setup for development automation.

Can I use the same tox configuration for C++ extensions and docs-only projects?▼

You cannot use the exact same tox configuration for C++ extensions and docs-only projects without archetype variations. The configuration provides specific guidance for Full Python, C++ extension, Reduced Python, and C++ docs-only project types.

How do I set up tox environments for linting and testing across multiple Python versions?▼

To set up tox environments for linting and testing across multiple Python versions, define an envlist pattern and environment definitions within the tox.ini file. This automates the development workflow pipelines for the project.

Does tox configuration support dependency installation strategies for different project archetypes?▼

Tox configuration supports dependency installation strategies for different project archetypes by managing environment definitions and toolchain integration. It covers variations for Full Python, C++ extensions, and Reduced Python projects.