sbdchd · kodiakhq · Dec 21, 2025 · Dec 21, 2025 · Dec 21, 2025
diff --git a/Cargo.lock b/Cargo.lock
diff --git a/crates/squawk/src/reporter.rs b/crates/squawk/src/reporter.rs
@@ -91,10 +91,6 @@ fn render_lint_error<W: std::io::Write>(
     sql: &str,
 ) -> Result<()> {
     let renderer = Renderer::styled().decor_style(DecorStyle::Unicode);
-    let error_name = &err.rule_name;
-
-    let title = &err.message;
-
     let level = match err.level {
         ViolationLevel::Warning => Level::WARNING,
         ViolationLevel::Error => Level::ERROR,
@@ -105,7 +101,10 @@ fn render_lint_error<W: std::io::Write>(
         .fold(true)
         .annotation(AnnotationKind::Primary.span(err.range.into()));
 
-    let mut group = level.primary_title(title).id(error_name).element(snippet);
+    let mut group = level
+        .primary_title(&err.message)
+        .id(&err.rule_name)
+        .element(snippet);
 
     if let Some(help) = &err.help {
         group = group.element(Level::HELP.message(help));

diff --git a/crates/squawk_linter/src/rules/ban_uncommitted_transaction.rs b/crates/squawk_linter/src/rules/ban_uncommitted_transaction.rs
@@ -53,7 +53,7 @@ BEGIN;
 CREATE TABLE users (id bigint);
         "#;
         assert_snapshot!(lint_errors(sql, Rule::BanUncommittedTransaction), @r"
-        error[BanUncommittedTransaction]: Transaction never committed or rolled back.
+        warning[ban-uncommitted-transaction]: Transaction never committed or rolled back.
           ╭▸ 
         2 │ BEGIN;
           │ ━━━━━
@@ -105,7 +105,7 @@ BEGIN;
 CREATE TABLE posts (id bigint);
         "#;
         assert_snapshot!(lint_errors(sql, Rule::BanUncommittedTransaction), @r"
-        error[BanUncommittedTransaction]: Transaction never committed or rolled back.
+        warning[ban-uncommitted-transaction]: Transaction never committed or rolled back.
           ╭▸ 
         6 │ BEGIN;
           │ ━━━━━
@@ -125,7 +125,7 @@ START TRANSACTION;
 CREATE TABLE users (id bigint);
         "#;
         assert_snapshot!(lint_errors(sql, Rule::BanUncommittedTransaction), @r"
-        error[BanUncommittedTransaction]: Transaction never committed or rolled back.
+        warning[ban-uncommitted-transaction]: Transaction never committed or rolled back.
           ╭▸ 
         2 │ START TRANSACTION;
           │ ━━━━━━━━━━━━━━━━━
@@ -155,7 +155,7 @@ BEGIN WORK;
 CREATE TABLE users (id bigint);
         "#;
         assert_snapshot!(lint_errors(sql, Rule::BanUncommittedTransaction), @r"
-        error[BanUncommittedTransaction]: Transaction never committed or rolled back.
+        warning[ban-uncommitted-transaction]: Transaction never committed or rolled back.
           ╭▸ 
         2 │ BEGIN WORK;
           │ ━━━━━━━━━━

diff --git a/crates/squawk_linter/src/rules/require_timeout_settings.rs b/crates/squawk_linter/src/rules/require_timeout_settings.rs
@@ -123,7 +123,7 @@ mod test {
 ALTER TABLE t ADD COLUMN c BOOLEAN;
         "#;
         assert_snapshot!(lint_errors(sql, Rule::RequireTimeoutSettings), @r"
-        error[RequireTimeoutSettings]: Missing `set lock_timeout` before potentially slow operations
+        warning[require-timeout-settings]: Missing `set lock_timeout` before potentially slow operations
           ╭▸ 
         2 │ ALTER TABLE t ADD COLUMN c BOOLEAN;
           │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
@@ -132,7 +132,7 @@ ALTER TABLE t ADD COLUMN c BOOLEAN;
           ╭╴
         2 + set lock_timeout = '1s';
           ╰╴
-        error[RequireTimeoutSettings]: Missing `set statement_timeout` before potentially slow operations
+        warning[require-timeout-settings]: Missing `set statement_timeout` before potentially slow operations
           ╭▸ 
         2 │ ALTER TABLE t ADD COLUMN c BOOLEAN;
           │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
@@ -151,7 +151,7 @@ SET statement_timeout = '5s';
 ALTER TABLE t ADD COLUMN c BOOLEAN;
         "#;
         assert_snapshot!(lint_errors(sql, Rule::RequireTimeoutSettings), @r"
-        error[RequireTimeoutSettings]: Missing `set lock_timeout` before potentially slow operations
+        warning[require-timeout-settings]: Missing `set lock_timeout` before potentially slow operations
           ╭▸ 
         3 │ ALTER TABLE t ADD COLUMN c BOOLEAN;
           │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
@@ -170,7 +170,7 @@ SET lock_timeout = '1s';
 ALTER TABLE t ADD COLUMN c BOOLEAN;
         "#;
         assert_snapshot!(lint_errors(sql, Rule::RequireTimeoutSettings), @r"
-        error[RequireTimeoutSettings]: Missing `set statement_timeout` before potentially slow operations
+        warning[require-timeout-settings]: Missing `set statement_timeout` before potentially slow operations
           ╭▸ 
         3 │ ALTER TABLE t ADD COLUMN c BOOLEAN;
           │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
@@ -218,7 +218,7 @@ SET foo.statement_timeout = '5s';
 ALTER TABLE t ADD COLUMN c BOOLEAN;
         "#;
         assert_snapshot!(lint_errors(sql, Rule::RequireTimeoutSettings), @r"
-        error[RequireTimeoutSettings]: Missing `set lock_timeout` before potentially slow operations
+        warning[require-timeout-settings]: Missing `set lock_timeout` before potentially slow operations
           ╭▸ 
         4 │ ALTER TABLE t ADD COLUMN c BOOLEAN;
           │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
@@ -227,7 +227,7 @@ ALTER TABLE t ADD COLUMN c BOOLEAN;
           ╭╴
         2 + set lock_timeout = '1s';
           ╰╴
-        error[RequireTimeoutSettings]: Missing `set statement_timeout` before potentially slow operations
+        warning[require-timeout-settings]: Missing `set statement_timeout` before potentially slow operations
           ╭▸ 
         4 │ ALTER TABLE t ADD COLUMN c BOOLEAN;
           │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
@@ -246,7 +246,7 @@ SET lock_timeout = '1s';
 SET statement_timeout = '5s';
         "#;
         assert_snapshot!(lint_errors(sql, Rule::RequireTimeoutSettings), @r"
-        error[RequireTimeoutSettings]: Missing `set lock_timeout` before potentially slow operations
+        warning[require-timeout-settings]: Missing `set lock_timeout` before potentially slow operations
           ╭▸ 
         2 │ ALTER TABLE t ADD COLUMN c BOOLEAN;
           │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
@@ -255,7 +255,7 @@ SET statement_timeout = '5s';
           ╭╴
         2 + set lock_timeout = '1s';
           ╰╴
-        error[RequireTimeoutSettings]: Missing `set statement_timeout` before potentially slow operations
+        warning[require-timeout-settings]: Missing `set statement_timeout` before potentially slow operations
           ╭▸ 
         2 │ ALTER TABLE t ADD COLUMN c BOOLEAN;
           │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
@@ -273,7 +273,7 @@ SET statement_timeout = '5s';
 CREATE TYPE mood AS ENUM ('sad', 'ok', 'happy');
         "#;
         assert_snapshot!(lint_errors(sql, Rule::RequireTimeoutSettings), @r"
-        error[RequireTimeoutSettings]: Missing `set lock_timeout` before potentially slow operations
+        warning[require-timeout-settings]: Missing `set lock_timeout` before potentially slow operations
           ╭▸ 
         2 │ CREATE TYPE mood AS ENUM ('sad', 'ok', 'happy');
           │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
@@ -282,7 +282,7 @@ CREATE TYPE mood AS ENUM ('sad', 'ok', 'happy');
           ╭╴
         2 + set lock_timeout = '1s';
           ╰╴
-        error[RequireTimeoutSettings]: Missing `set statement_timeout` before potentially slow operations
+        warning[require-timeout-settings]: Missing `set statement_timeout` before potentially slow operations
           ╭▸ 
         2 │ CREATE TYPE mood AS ENUM ('sad', 'ok', 'happy');
           │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

diff --git a/.../snapshots/squawk_linter__rules__adding_field_with_default__test__arbitrary_func_err.snap b/.../snapshots/squawk_linter__rules__adding_field_with_default__test__arbitrary_func_err.snap
@@ -2,7 +2,7 @@
 source: crates/squawk_linter/src/rules/adding_field_with_default.rs
 expression: "lint_errors(sql, Rule::AddingFieldWithDefault)"
 ---
-error[AddingFieldWithDefault]: Adding a generated column requires a table rewrite with an `ACCESS EXCLUSIVE` lock. In Postgres versions 11+, non-VOLATILE DEFAULTs can be added without a rewrite.
+warning[adding-field-with-default]: Adding a generated column requires a table rewrite with an `ACCESS EXCLUSIVE` lock. In Postgres versions 11+, non-VOLATILE DEFAULTs can be added without a rewrite.
   ╭▸ 
 3 │ ALTER TABLE "core_recipe" ADD COLUMN "foo" jsonb DEFAULT myjsonb();
   │                                                          ━━━━━━━━━

diff --git a/.../squawk_linter__rules__adding_field_with_default__test__default_random_with_args_err.snap b/.../squawk_linter__rules__adding_field_with_default__test__default_random_with_args_err.snap
@@ -2,7 +2,7 @@
 source: crates/squawk_linter/src/rules/adding_field_with_default.rs
 expression: "lint_errors(sql, Rule::AddingFieldWithDefault)"
 ---
-error[AddingFieldWithDefault]: Adding a generated column requires a table rewrite with an `ACCESS EXCLUSIVE` lock. In Postgres versions 11+, non-VOLATILE DEFAULTs can be added without a rewrite.
+warning[adding-field-with-default]: Adding a generated column requires a table rewrite with an `ACCESS EXCLUSIVE` lock. In Postgres versions 11+, non-VOLATILE DEFAULTs can be added without a rewrite.
   ╭▸ 
 3 │ ALTER TABLE "core_recipe" ADD COLUMN "foo" timestamptz DEFAULT now(123);
   │                                                                ━━━━━━━━

diff --git a/.../snapshots/squawk_linter__rules__adding_field_with_default__test__default_uuid_error.snap b/.../snapshots/squawk_linter__rules__adding_field_with_default__test__default_uuid_error.snap
@@ -2,7 +2,7 @@
 source: crates/squawk_linter/src/rules/adding_field_with_default.rs
 expression: "lint_errors(sql, Rule::AddingFieldWithDefault)"
 ---
-error[AddingFieldWithDefault]: Adding a generated column requires a table rewrite with an `ACCESS EXCLUSIVE` lock. In Postgres versions 11+, non-VOLATILE DEFAULTs can be added without a rewrite.
+warning[adding-field-with-default]: Adding a generated column requires a table rewrite with an `ACCESS EXCLUSIVE` lock. In Postgres versions 11+, non-VOLATILE DEFAULTs can be added without a rewrite.
   ╭▸ 
 2 │ ALTER TABLE "core_recipe" ADD COLUMN "foo" integer DEFAULT uuid();
   │                                                            ━━━━━━

diff --git a/...squawk_linter__rules__adding_field_with_default__test__default_uuid_error_multi_stmt.snap b/...squawk_linter__rules__adding_field_with_default__test__default_uuid_error_multi_stmt.snap
@@ -2,7 +2,7 @@
 source: crates/squawk_linter/src/rules/adding_field_with_default.rs
 expression: "lint_errors(sql, Rule::AddingFieldWithDefault)"
 ---
-error[AddingFieldWithDefault]: Adding a generated column requires a table rewrite with an `ACCESS EXCLUSIVE` lock. In Postgres versions 11+, non-VOLATILE DEFAULTs can be added without a rewrite.
+warning[adding-field-with-default]: Adding a generated column requires a table rewrite with an `ACCESS EXCLUSIVE` lock. In Postgres versions 11+, non-VOLATILE DEFAULTs can be added without a rewrite.
   ╭▸ 
 2 │ alter table t set logged, add column c integer default uuid();
   │                                                        ━━━━━━

diff --git a/...ots/squawk_linter__rules__adding_field_with_default__test__default_volatile_func_err.snap b/...ots/squawk_linter__rules__adding_field_with_default__test__default_volatile_func_err.snap
@@ -2,7 +2,7 @@
 source: crates/squawk_linter/src/rules/adding_field_with_default.rs
 expression: "lint_errors(sql, Rule::AddingFieldWithDefault)"
 ---
-error[AddingFieldWithDefault]: Adding a generated column requires a table rewrite with an `ACCESS EXCLUSIVE` lock. In Postgres versions 11+, non-VOLATILE DEFAULTs can be added without a rewrite.
+warning[adding-field-with-default]: Adding a generated column requires a table rewrite with an `ACCESS EXCLUSIVE` lock. In Postgres versions 11+, non-VOLATILE DEFAULTs can be added without a rewrite.
   ╭▸ 
 3 │ ALTER TABLE "core_recipe" ADD COLUMN "foo" boolean DEFAULT random();
   │                                                            ━━━━━━━━

diff --git a/...s/squawk_linter__rules__adding_field_with_default__test__docs_example_error_on_pg_11.snap b/...s/squawk_linter__rules__adding_field_with_default__test__docs_example_error_on_pg_11.snap
@@ -2,7 +2,7 @@
 source: crates/squawk_linter/src/rules/adding_field_with_default.rs
 expression: "lint_errors_with(sql, LinterSettings\n{\n    pg_version: \"11\".parse().expect(\"Invalid PostgreSQL version\"),\n    ..Default::default()\n},)"
 ---
-error[AddingFieldWithDefault]: Adding a generated column requires a table rewrite with an `ACCESS EXCLUSIVE` lock. In Postgres versions 11+, non-VOLATILE DEFAULTs can be added without a rewrite.
+warning[adding-field-with-default]: Adding a generated column requires a table rewrite with an `ACCESS EXCLUSIVE` lock. In Postgres versions 11+, non-VOLATILE DEFAULTs can be added without a rewrite.
   ╭▸ 
 3 │ ALTER TABLE "core_recipe" ADD COLUMN "foo" integer DEFAULT 10;
   │                                                            ━━

diff --git a/...napshots/squawk_linter__rules__adding_field_with_default__test__generated_stored_err.snap b/...napshots/squawk_linter__rules__adding_field_with_default__test__generated_stored_err.snap
@@ -2,7 +2,7 @@
 source: crates/squawk_linter/src/rules/adding_field_with_default.rs
 expression: "lint_errors(sql, Rule::AddingFieldWithDefault)"
 ---
-error[AddingFieldWithDefault]: Adding a generated column requires a table rewrite with an `ACCESS EXCLUSIVE` lock. In Postgres versions 11+, non-VOLATILE DEFAULTs can be added without a rewrite.
+warning[adding-field-with-default]: Adding a generated column requires a table rewrite with an `ACCESS EXCLUSIVE` lock. In Postgres versions 11+, non-VOLATILE DEFAULTs can be added without a rewrite.
   ╭▸ 
 3 │ ADD COLUMN bar numeric GENERATED ALWAYS AS (bar + baz) STORED;
   │                        ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

diff --git a/...quawk_linter__rules__adding_foreign_key_constraint__test__add_column_references_lock.snap b/...quawk_linter__rules__adding_foreign_key_constraint__test__add_column_references_lock.snap
@@ -2,7 +2,7 @@
 source: crates/squawk_linter/src/rules/adding_foreign_key_constraint.rs
 expression: "lint_errors(sql, Rule::AddingForeignKeyConstraint)"
 ---
-error[AddingForeignKeyConstraint]: Adding a foreign key constraint requires a table scan and a `SHARE ROW EXCLUSIVE` lock on both tables, which blocks writes to each table.
+warning[adding-foreign-key-constraint]: Adding a foreign key constraint requires a table scan and a `SHARE ROW EXCLUSIVE` lock on both tables, which blocks writes to each table.
   ╭▸ 
 3 │ ALTER TABLE "emails" ADD COLUMN "user_id" INT REFERENCES "user" ("id");
   │                                               ━━━━━━━━━━━━━━━━━━━━━━━━

diff --git a/..._linter__rules__adding_foreign_key_constraint__test__add_foreign_key_constraint_lock.snap b/..._linter__rules__adding_foreign_key_constraint__test__add_foreign_key_constraint_lock.snap
@@ -2,7 +2,7 @@
 source: crates/squawk_linter/src/rules/adding_foreign_key_constraint.rs
 expression: "lint_errors(sql, Rule::AddingForeignKeyConstraint)"
 ---
-error[AddingForeignKeyConstraint]: Adding a foreign key constraint requires a table scan and a `SHARE ROW EXCLUSIVE` lock on both tables, which blocks writes to each table.
+warning[adding-foreign-key-constraint]: Adding a foreign key constraint requires a table scan and a `SHARE ROW EXCLUSIVE` lock on both tables, which blocks writes to each table.
   ╭▸ 
 4 │ ALTER TABLE "email" ADD CONSTRAINT "fk_user" FOREIGN KEY ("user_id") REFERENCES "user" ("id");
   │                         ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

diff --git a/...snapshots/squawk_linter__rules__adding_not_null_field__test__regression_gh_issue_519.snap b/...snapshots/squawk_linter__rules__adding_not_null_field__test__regression_gh_issue_519.snap
@@ -2,7 +2,7 @@
 source: crates/squawk_linter/src/rules/adding_not_null_field.rs
 expression: "lint_errors(sql, Rule::AddingNotNullableField)"
 ---
-error[AddingNotNullableField]: Setting a column `NOT NULL` blocks reads while the table is scanned.
+warning[adding-not-nullable-field]: Setting a column `NOT NULL` blocks reads while the table is scanned.
   ╭▸ 
 4 │ ALTER TABLE my_table ALTER COLUMN my_column SET NOT NULL;
   │                                             ━━━━━━━━━━━━

diff --git a/.../src/rules/snapshots/squawk_linter__rules__adding_not_null_field__test__set_not_null.snap b/.../src/rules/snapshots/squawk_linter__rules__adding_not_null_field__test__set_not_null.snap
@@ -2,7 +2,7 @@
 source: crates/squawk_linter/src/rules/adding_not_null_field.rs
 expression: "lint_errors(sql, Rule::AddingNotNullableField)"
 ---
-error[AddingNotNullableField]: Setting a column `NOT NULL` blocks reads while the table is scanned.
+warning[adding-not-nullable-field]: Setting a column `NOT NULL` blocks reads while the table is scanned.
   ╭▸ 
 2 │ ALTER TABLE "core_recipe" ALTER COLUMN "foo" SET NOT NULL;
   │                                              ━━━━━━━━━━━━

diff --git a/...apshots/squawk_linter__rules__adding_primary_key_constraint__test__plain_primary_key.snap b/...apshots/squawk_linter__rules__adding_primary_key_constraint__test__plain_primary_key.snap
@@ -2,7 +2,7 @@
 source: crates/squawk_linter/src/rules/adding_primary_key_constraint.rs
 expression: "lint_errors(sql, Rule::AddingSerialPrimaryKeyField)"
 ---
-error[AddingSerialPrimaryKeyField]: Adding a primary key constraint requires an `ACCESS EXCLUSIVE` lock that will block all reads and writes to the table while the primary key index is built.
+warning[adding-serial-primary-key-field]: Adding a primary key constraint requires an `ACCESS EXCLUSIVE` lock that will block all reads and writes to the table while the primary key index is built.
   ╭▸ 
 2 │ ALTER TABLE items ADD PRIMARY KEY (id);
   │                       ━━━━━━━━━━━━━━━━

diff --git a/...pshots/squawk_linter__rules__adding_primary_key_constraint__test__serial_primary_key.snap b/...pshots/squawk_linter__rules__adding_primary_key_constraint__test__serial_primary_key.snap
@@ -2,7 +2,7 @@
 source: crates/squawk_linter/src/rules/adding_primary_key_constraint.rs
 expression: "lint_errors(sql, Rule::AddingSerialPrimaryKeyField)"
 ---
-error[AddingSerialPrimaryKeyField]: Adding a primary key constraint requires an `ACCESS EXCLUSIVE` lock that will block all reads and writes to the table while the primary key index is built.
+warning[adding-serial-primary-key-field]: Adding a primary key constraint requires an `ACCESS EXCLUSIVE` lock that will block all reads and writes to the table while the primary key index is built.
   ╭▸ 
 2 │         ALTER TABLE a ADD COLUMN b SERIAL PRIMARY KEY;
   │                                           ━━━━━━━━━━━

diff --git a/...napshots/squawk_linter__rules__adding_required_field__test__not_null_without_default.snap b/...napshots/squawk_linter__rules__adding_required_field__test__not_null_without_default.snap
@@ -2,7 +2,7 @@
 source: crates/squawk_linter/src/rules/adding_required_field.rs
 expression: "lint_errors(sql, Rule::AddingRequiredField)"
 ---
-error[AddingRequiredField]: Adding a new column that is `NOT NULL` and has no default value to an existing table effectively makes it required.
+warning[adding-required-field]: Adding a new column that is `NOT NULL` and has no default value to an existing table effectively makes it required.
   ╭▸ 
 2 │ ALTER TABLE "recipe" ADD COLUMN "public" boolean NOT NULL;
   │                      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

diff --git a/...ules/snapshots/squawk_linter__rules__ban_alter_domain_with_add_constraint__test__err.snap b/...ules/snapshots/squawk_linter__rules__ban_alter_domain_with_add_constraint__test__err.snap
@@ -2,7 +2,7 @@
 source: crates/squawk_linter/src/rules/ban_alter_domain_with_add_constraint.rs
 expression: "lint_errors(sql, Rule::BanAlterDomainWithAddConstraint)"
 ---
-error[BanAlterDomainWithAddConstraint]: Domains with constraints have poor support for online migrations. Use table and column constraints instead.
+warning[ban-alter-domain-with-add-constraint]: Domains with constraints have poor support for online migrations. Use table and column constraints instead.
   ╭▸ 
 2 │      ALTER DOMAIN domain_name ADD CONSTRAINT constraint_name CHECK (value > 0);
   ╰╴                              ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━