cc-python-dev

Applies Python coding standards for type annotations, Pydantic models, pytest, and uv toolchains.

1.0k|109|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/doccker/cc-use-exp --skill cc-python-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cc-python-dev
Source: https://github.com/doccker/cc-use-exp/tree/main/.codex/skills/cc-python-dev
Command: npx skills add https://github.com/doccker/cc-use-exp --skill cc-python-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Python codebases often drift into inconsistent typing, unclear data model boundaries, weak test coverage, and toolchain fragmentation. This Skill gives the AI a consistent set of Python development conventions so edits follow your project's standards instead of ad-hoc habits.

Core Features & Use Cases

  • Type Annotation Guidance: Prioritizes type information on public interfaces, core models, and complex return values, with explicit handling of Any trade-offs.
  • Pydantic & Data Model Boundaries: Keeps input/output models separated and validation logic clear without over-engineered validators.
  • pytest Practices: Encourages behavior-expressive test names, parametrization, local fixtures, and coverage of edge cases and exception paths.
  • Toolchain Consistency: Aligns with existing project tooling, especially uv-based dependency, run, and test entry points.
  • Use Case: When asking the AI to add a new API endpoint in a FastAPI-style project, the Skill ensures typed signatures, separated request/response models, and matching pytest coverage.

Quick Start

Ask the AI to edit or add Python code in this project while following the cc-python-dev conventions for typing, Pydantic models, and pytest coverage.

Frequently Asked Questions about cc-python-dev

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

FAQPage Schema
How do I enforce Python type annotation standards in AI-assisted coding?

This Skill instructs the AI to prioritize type annotations on public interfaces, core models, and complex return values. When full typing is impractical, it narrows risk scope locally rather than abandoning types globally, and treats Any as an explicit trade-off.

What pytest practices should AI-generated tests follow?

Tests should have behavior-expressive names, prefer parametrization and local fixtures over global coupling, and cover exception paths and boundary inputs. The Skill directs the AI to focus test coverage on affected behavior rather than superficial cases.

How should Pydantic models be structured for input and output?

Input and output models should be kept separate with clear field definitions, defaults, and validation logic. Complex validators are only written when genuinely needed, avoiding mixed-semantics models across boundaries.

Does this Skill work with the uv Python toolchain?

Yes, it explicitly covers uv-based workflows. The guidance is to keep dependency management, run commands, and test entry points consistent with the project's existing uv setup rather than introducing new tools without proven benefit.

When should I not use this Python development Skill?

It is not intended for formal code review, fix/debug workflows, or operational risk decisions. It also does not apply to non-Python language concerns, as its scope is limited to Python editing conventions.