auto-import-rules

Enforces Go import conventions and formatting for dlt project files.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Thanhhuong0209/DLT-Normalization --skill auto-import-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-import-rules
Source: https://github.com/Thanhhuong0209/DLT-Normalization/tree/main/.claude/skills/auto-import-rules
Command: npx skills add https://github.com/Thanhhuong0209/DLT-Normalization --skill auto-import-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces consistent Python import ordering and conventions within the dlt project, improving code readability and maintainability.

Core Features & Use Cases

  • Standardized Imports: Ensures imports are grouped logically (stdlib, third-party, local dlt).
  • Logging Convention: Promotes the use of dlt.common.logger over the standard logging module.
  • Type Checking Imports: Manages optional dependencies for type annotations correctly.
  • Use Case: When adding a new feature that requires importing external libraries, this Skill will automatically format the imports according to the project's established rules.

Quick Start

Use the auto-import-rules skill to format imports in the file dlt/common/utils.py.

Frequently Asked Questions about auto-import-rules

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

FAQPage Schema
How do I enforce Python import conventions in a dlt project?

To enforce Python import conventions in a dlt project, use this Skill to automatically format imports into standard library, third-party, and local groupings within the dlt/ and tests/ directories. This ensures code maintainability and clarity by applying strict import ordering rules.

What is the correct Python import ordering for dlt code style?

Correct Python import ordering for dlt code style requires grouping imports into standard library, third-party, and local dlt categories. This mechanism improves code readability and maintainability across all Python files in the dlt/ and tests/ directories.

Does the dlt project use a specific logger over the standard Python logging module?

Yes, the dlt project logging convention promotes using `dlt.common.logger` over the standard Python `logging` module. This ensures consistent logging practices and proper integration with the dlt framework's internal conventions.

How do I manage type checking imports for optional dependencies in Python?

To manage type checking imports for optional dependencies in Python, this Skill enforces specific import styles for type annotations. It ensures optional dependencies are handled correctly without breaking the standard library, third-party, and local import groupings.

Can I apply import linting rules to files outside the dlt/ and tests/ directories?

No, these import linting rules specifically apply to Python files within the dlt/ and tests/ directories. The Skill enforces dlt project conventions strictly within these specified paths to maintain code style and clarity.