Skip to content
Skills Library
Programming · Tool integration

sqlty-server

/sqlty-server

Run sqlty in an editor with sqlty server, the language server, and the VS Code extension. Use when setting up sqlty in VS Code, Cursor, VSCodium, Neovim, Vim, Helix, Emacs or another LSP client, highlighting SQL in query strings, fixing a query on save with source.fixAll.sqlty, formatting query strings with source.format.sqlty, showing sqlty breaking findings while editing, or when the editor reports nothing or different diagnostics than sqlty check.

Repository
sqlty ↗
Licence
MIT
Last repository change
13.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
4
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Run sqlty in an editor with sqlty server, the language server, and the VS Code extension. Use when setting up sqlty in VS Code, Cursor, VSCodium, Neovim, Vim, Helix, Emacs or another LSP client, highlighting SQL in query strings, fixing a query on save with source.fixAll.sqlty, formatting query strings with source.format.sqlty, showing sqlty breaking findings while editing, or when the editor reports nothing or different diagnostics than sqlty check.

Original author description

Run sqlty in an editor with sqlty server, the language server, and the VS Code extension. Use when setting up sqlty in VS Code, Cursor, VSCodium, Neovim, Vim, Helix, Emacs or another LSP client, highlighting SQL in query strings, fixing a query on save with source.fixAll.sqlty, formatting query strings with source.format.sqlty, showing sqlty breaking findings while editing, or when the editor reports nothing or different diagnostics than sqlty check.

How it works

  1. VS Code
  2. Other editors
  3. Breaking changes while editing
  4. Nothing is reported
  5. Reference
Original SKILL.md headings · 112 lines, 616 words
SKILL.md preview
---
name: sqlty-server
description: Run sqlty in an editor with sqlty server, the language server, and the VS Code extension. Use when setting up sqlty in VS Code, Cursor, VSCodium, Neovim, Vim, Helix, Emacs or another LSP client, highlighting SQL in query strings, fixing a query on save with source.fixAll.sqlty, formatting query strings with source.format.sqlty, showing sqlty breaking findings while editing, or when the editor reports nothing or different diagnostics than sqlty check.
---

# sqlty server

`sqlty server` is a language server on standard input and output. It reports what
`sqlty check` reports while you type, each diagnostic under the name, row type or
query it is about, with the fix of `sqlty check --fix` as a quick fix. In a query
string it completes table and column names, and hover shows a column's type, a table's
columns or a result column's inference rule.

Run `sqlty version`: this skill may be newer or older than the installed sqlty.
When it and `sqlty server --help` disagree, trust the command.

```toml
[tool.sqlty]
schema = "schema.sql"
```

`schema.sql`:

```sql
CREATE TABLE users (id INTEGER PRIMARY KEY, name TEXT NOT NULL);
```

```python
from sqlty import SQL

# error: [unknown-column] "column `nmae` does not exist in `users`"
q = SQL[tuple[int, str]]("--sql\nSELECT id, nmae FROM users")
```

## VS Code

Install **sqlty** (`jirikuncar.sqlty`) from the Visual Studio Marketplace, or from
Open VSX in Cursor, VSCodium and other builds of VS Code:

```bash
code --install-extension jirikuncar.sqlty
```

The extension bundles no sqlty. It runs the one your project pins, so add it to the
project's environment (`uv add --dev sqlty`) and the editor reports what CI reports.

| Setting | Meaning |
|---------|---------|
| `sqlty.path` | `sqlty` executables to try first |
| `sqlty.interpreter` | The interpreter whose `sqlty` runs; empty is the one the Python extension selects |
| `sqlty.breaking.against` | A baseline for `sqlty breaking`: a git revision, a `--save` snapshot or schema files |
| `sqlty.breaking.direction` | `both` (default), `forward` or `backward` |
| `sqlty.trace.server` | `off` (default), `messages` or `verbose`: log the protocol in the **sqlty** output channel |

Fix a file on every save with `source.fixAll.sqlty`, which is `sqlty check --fix`, and lay
out its query strings with `source.format.sqlty`, which is `sqlty format`:

```json
{
  "[python]": {
    "editor.codeActionsOnSave": {
      "source.fixAll.sqlty": "explicit",
      "source.format.sqlty": "explicit"
    }
  }
}
```

## Other editors

Any LSP client can run `sqlty server` for Python files. For Neovim 0.11:

```lua
vim.lsp.config("sqlty", {
  cmd = { "sqlty", "server" },
  filetypes = { "python" },
  root_markers = { "pyproject.toml", ".git" },
  init_options = { breaking = { against = "main", direction = "both" } },
})
vim.lsp.enable("sqlty")
```

`init_options` is optional: without it, no baseline is checked. The server also
colors the SQL of checked strings with semantic tokens; `highlighting = { enable = false }`
turns that off. VS Code shows one semantic-token provider per file, so the extension
keeps it off there and highlights strings marked `--sql` with a grammar instead.

For nvim-lint, Vim (vim-lsp, ALE, coc.nvim, `:make`), Helix and Emacs (Eglot, lsp-mode), see
[Neovim, Vim, Helix and Emacs](https://sqlty.kuncar.dev/recipes/editors/).
Eglot runs one server per major mode: run sqlty next to ty or ruff through
`rass python -- sqlty server`, with sqlty's highlighting off, or use lsp-mode with
sqlty as an add-on.

## Breaking changes while editing

With a baseline, the editor also shows what `sqlty breaking` reports. A finding's
source is `sqlty breaking (forward)` or `sqlty breaking (backward)`, and it has no
quick fix: the fix belongs to the migration or the code, depending on which ships
first (see `sqlty-breaking`). The server resolves `main` when the project loads:
when it moves, save a schema or run **sqlty: Restart Server**.

## Nothing is reported

- Run `sqlty check <file>` in a terminal. When it reports the problem and the
  editor doesn't, the editor runs another `sqlty`: check `sqlty.path` and
  `sqlty.interpreter`, then run **sqlty: Restart Server**.
- Saving `pyproject.toml` or a `.sql` file reloads the settings and schema
  without a restart.
- The extension does not run in Restricted Mode: trust the folder.

## Reference

- [VS Code](https://sqlty.kuncar.dev/recipes/vscode/)
- [Neovim, Vim, Helix and Emacs](https://sqlty.kuncar.dev/recipes/editors/)
- [Breaking schema changes](https://sqlty.kuncar.dev/guide/breaking-changes/)

Versions

The database has no other skills named sqlty-server.

Database snapshot: 13.11.2026 · package version d301f2ac3eb4 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100sqlty
    Write, type and check raw SQL in Python with sqlty. Use when adding or editing a query in a project that uses sqlty (strings starting with --sql, SQL[T] or SQLTemplate[T] wrappers, a [tool.sqlty] section), when generating Python row types for a query, or when checking that…
  • 100sqlty-rewrite
    Wrap --sql query strings as SQL[T] with sqlty rewrite, update or remove the wrappers, and keep them in sync after editing a query. Use when writing a new SQL query in Python, editing the SQL inside an SQL[T] wrapper, committing or removing wrappers (sqlty rewrite, sqlty strip,…
  • 100neovim
    Neovim is a terminal text editor configured in Lua, with a built-in LSP client, Treesitter parsing and, since 0.12, a built-in plugin manager (vim.pack). Use this skill to install Neovim, write or repair an init.lua, add plugins, wire up language servers with vim.lsp.config and…
  • 100intlayer-dev-tools
    Sets up Intlayer developer tooling - ESLint / oxlint rules, the Language Server (LSP), the VS Code extension, the MCP server, CI/CD automation and the Chrome extension. Use when the user asks to "lint hardcoded strings", "setup Go-to-Definition for dictionary keys", "install the…
  • 100helix-interact
    Test Helix editor config changes, debug LSP issues, or observe editor behavior by running Helix in a tmux session. Use when iterating on helix config.toml, languages.toml, Steel scripts, or troubleshooting language server problems.
  • 86multi-language-dev-env
    Configure Emacs as an effective IDE for multiple programming languages. Trigger on phrases like "emacs development environment", "multi-language emacs", "lsp in emacs", "eglot setup", "emacs ide configuration".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.