formatter

To automatically format Python and SQL code, this skill applies ruff to Python files and sqlfluff to SQL files. It enforces project-specific style guidelines and validates the output by running linter checks after formatting.

Yes, you can use ruff and sqlfluff together for pre-commit code formatting. This skill integrates both linters to automatically apply consistent formatting and enforce style rules across your Python and SQL codebases.

The best way to format Python scripts while protecting generated files is using an automated formatter with safety guardrails. This skill skips generated files like migrations and lock files to avoid unintended changes during code cleanup.

Yes, code formatting runs a linter check after applying style changes. This post-format validation process ensures that any remaining style issues are caught immediately after the initial formatting is applied to your files.

You should not use automated code formatting on generated files or lock files within your data processing scripts. The tool explicitly skips these file types to prevent unintended modifications to auto-generated database migrations.