core

Enforce PEP 8, type hints, docstrings, and black or ruff formatting for Python code.

4|2|Updated Dec 28, 2025
One-click install
npx skills add https://github.com/lazygophers/ccplugin --skill core-lazygophers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: core
Source: https://github.com/lazygophers/ccplugin/tree/main/plugins/languages/python/skills/core
Command: npx skills add https://github.com/lazygophers/ccplugin --skill core-lazygophers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces essential Python development standards, ensuring code quality, maintainability, and adherence to best practices before any Python code is written or reviewed.

Core Features & Use Cases

  • PEP 8 Compliance: Guides developers to follow the official Python style guide.
  • Type Hinting Enforcement: Promotes the use of type annotations for better code clarity and static analysis.
  • Documentation Standards: Mandates docstrings for functions and classes.
  • Code Formatting: Recommends tools like black and ruff for consistent formatting.
  • Use Case: When starting a new Python project or contributing to an existing one, load this Skill to ensure all new code adheres to established quality benchmarks.

Quick Start

Ensure all new Python code adheres to PEP 8, uses type hints, and includes docstrings.

Frequently Asked Questions about core

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

FAQPage Schema
How do I enforce PEP 8 and type hinting in a new Python project?

To enforce PEP 8 and type hinting in Python projects, apply core development standards that mandate type annotations and use formatting tools like black and ruff to ensure code quality and static analysis readiness.

What is the best way to maintain Python docstrings and code formatting standards?

The best way to maintain Python docstrings and code formatting is to enforce development standards requiring documentation for all functions and classes, paired with automated formatting tools like black and ruff for consistency.

Does this Python development standards approach support existing codebase reviews?

Yes, this Python development standards approach supports existing codebase reviews by applying PEP 8 compliance, type hinting, and docstring mandates to ensure all new code adheres to established quality benchmarks during contributions.

Why should I use black and ruff for Python code formatting?

You should use black and ruff for Python code formatting because they enforce consistent style and static analysis readiness, satisfying requirements for code quality, readability, and maintainability across all development scenarios.

Can I apply these Python core standards to any Python code development scenario?

Yes, you can apply these Python core standards to any code development scenario requiring adherence to best practices, as they enforce PEP 8, type hinting, and docstring standards universally for maintainability.