coding-standards

tumma72's avatarfrom tumma72

Python code style, formatting, linting, and type hints for GMailArchiver. Use when writing Python code, fixing ruff or mypy errors, adding type hints, formatting imports, or reviewing code quality. Triggers on: style, format, lint, ruff, mypy, type hint, import order, line length, docstring.

⭐2stars🔀0forks📁View on GitHub🕐Updated Dec 23, 2025⬇️1downloads

When & Why to Use This Skill

This Claude skill ensures high-quality Python development for the GMailArchiver project by enforcing strict coding standards, linting rules, and type-checking protocols. It optimizes the development workflow by integrating tools like Ruff and Mypy, helping developers maintain consistent code style, fix formatting issues, and adhere to project-specific architectural patterns.

Use Cases

  • Automated Code Quality Checks: Use the skill to identify and fix linting errors or formatting inconsistencies using Ruff, ensuring compliance with the project's 100-character line length and import sorting rules.
  • Type Safety Enforcement: Leverage Mypy integration to add and verify strict type hints, reducing runtime bugs and improving code readability for Python 3.14+ environments.
  • Standardized Code Reviews: Apply the definitive guidelines from docs/CODING.md during pull request reviews to ensure naming conventions, docstrings, and error handling patterns are consistently followed.
  • Developer Onboarding: Provide a quick-reference guide for new contributors to learn the specific quality commands and tooling requirements (uv, ruff, mypy) used in the GMailArchiver repository.
namecoding-standards
description>-
formatting imports, or reviewing code quality. Triggers onstyle, format,

Coding Standards for GMailArchiver

This skill provides guidance on coding standards and style conventions.

Source Documentation

Always read the authoritative source:

docs/CODING.md - The definitive coding standards document containing:

  • Code style and formatting rules
  • Naming conventions
  • Import organization
  • Type hint requirements
  • Docstring standards
  • Error handling patterns
  • Logging conventions

Quick Reference

Key tools used:

  • ruff - Linting and formatting (line length: 100)
  • mypy - Type checking (strict mode)
  • Python 3.14+ - Target version

Quality Commands

# Check linting
uv run ruff check .

# Auto-fix linting issues
uv run ruff check . --fix

# Check formatting
uv run ruff format --check .

# Apply formatting
uv run ruff format .

# Type checking
uv run mypy src/gmailarchiver

Usage

When writing code:

  1. Read docs/CODING.md for current coding standards
  2. Run quality checks before committing
  3. If standards change, update docs/CODING.md (not this skill)

The source documentation is the single source of truth - this skill just points you there.