sqlfluff

Lint standalone SQL files with sqlfluff and project dialect configuration.

Updated Jun 19, 2026
One-click install
npx skills add https://github.com/lciacci/tessera --skill sqlfluff-lciacci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sqlfluff
Source: https://github.com/lciacci/tessera/tree/main/skills/sqlfluff
Command: npx skills add https://github.com/lciacci/tessera --skill sqlfluff-lciacci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps detect genuine SQL syntax, dialect, and formatting issues without treating every linter warning as a defect.

Core Features & Use Cases

  • Dialect-Aware Linting: Lint standalone SQL files with the project's configured SQL dialect.
  • Contextual Review: Distinguish meaningful parse and portability problems from layout noise or context-dependent false positives.
  • Safe Formatting Guidance: Use existing project configuration and warn-only checks for migrations, dbt models, analytics queries, and other frequently edited SQL files.

Quick Start

Ask the sqlfluff skill to lint the SQL file you are currently reviewing using the project's configuration and explain which findings are genuine defects.

Frequently Asked Questions about sqlfluff

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

FAQPage Schema
How do I lint SQL files without treating every formatting warning as an error?

SQL linting can distinguish genuine syntax and portability issues from layout noise by applying dialect-aware checks with project configuration, using warn-only rules for frequently edited files like dbt models.

Can I use sqlfluff to lint dbt models and database migration scripts?

Yes, sqlfluff applies to dbt models, database migrations, and analytics queries by detecting syntax and formatting issues based on the explicitly selected SQL dialect and project configuration.

What is dialect-aware SQL formatting and why do I need it for postgres queries?

Dialect-aware SQL formatting contextualizes parse issues by validating syntax against a specific SQL dialect like postgres, preventing false positives caused by applying generic SQL rules to dialect-specific code.

Does sqlfluff work with SQL embedded inside application code string literals?

No, sqlfluff does not process SQL embedded in application-code string literals; it only lints standalone SQL files including migrations, dbt models, and analytics queries.

How do I configure SQL linting rules to avoid false positives in analytics queries?

SQL linting uses existing project configuration and an explicitly selected dialect to interpret findings in their surrounding context, filtering out context-dependent false positives in analytics queries.

Why does SQL linting report parsing errors on valid postgres syntax?

SQL linting reports parsing errors when the configured SQL dialect does not match the actual syntax used; selecting the correct postgres dialect ensures valid syntax is interpreted properly without false defects.