python-engineering-standards

Enforce PEP 8, type hints, and security best practices in Python code.

1|Updated May 19, 2026
One-click install
npx skills add https://github.com/victormacaubas/data-engineering-skills --skill python-engineering-standards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: python-engineering-standards
Source: https://github.com/victormacaubas/data-engineering-skills/tree/main/skills/python-engineering-standards
Command: npx skills add https://github.com/victormacaubas/data-engineering-skills --skill python-engineering-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ruff, mypy, pytest, pre-commit, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that Python code adheres to a canonical set of engineering standards, making it easier to read, maintain, and scale.

Core Features & Use Cases

  • Code Layout: Enforce PEP 8 style guidelines for indentation, naming conventions, and line length.
  • Type Hints: Use dataclasses and type hints for clarity and tooling support.
  • Security Standards: Implement security best practices such as parameterized queries and secure credential handling.
  • Testing and Tooling: Leverage Ruff, mypy, pytest, and pre-commit for automated code quality checks.
  • Use Case: When writing a new Python module, use this skill to ensure that your code follows the established standards.

Quick Start

Initialize a new Python project and apply the Python engineering standards using the python-engineering-standards skill.

Frequently Asked Questions about python-engineering-standards

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

FAQPage Schema
How do I enforce PEP 8 coding standards and type hints in a Python project?

Enforce PEP 8 coding standards and type hints by applying automated checks with Ruff and mypy. This Skill integrates these tools to validate code layout, indentation, naming conventions, and type hint clarity for production modules.

How do I set up automated Python code quality checks for production services?

Set up automated Python code quality checks by configuring pre-commit hooks to run Ruff, mypy, and pytest. This pipeline validates security practices, type consistency, and PEP 8 style guidelines before code changes are committed.

Does this Python coding standards skill work with data pipelines and CLI tools?

Yes, this Python coding standards skill supports common project layouts including data pipelines, services, and CLI tools. It applies security best practices and type hinting across these varied architectures.

What's the best way to implement security best practices like parameterized queries in Python?

Implement security best practices like parameterized queries and secure credential handling by following the canonical engineering standards defined by this skill. It provides reference scripts to guide secure production code development.

Do I need Python 3.11 to use Ruff and mypy for code quality checks?

Yes, you need Python 3.11 or higher to apply these engineering standards. The skill targets modern Python features like dataclasses and type hints, leveraging Ruff and mypy to enforce them.

Why use pre-commit hooks for Python type hints and PEP 8 style enforcement?

Use pre-commit hooks to automate PEP 8 style enforcement and type hint validation locally. Running Ruff and mypy before commits prevents low-quality code from entering the repository, reducing CI pipeline failures.