mit einem Klick
format
// Format SQL files using the syntaqlite formatter. Use when the user wants to format, reformat, or pretty-print SQL code.
// Format SQL files using the syntaqlite formatter. Use when the user wants to format, reformat, or pretty-print SQL code.
| name | format |
| description | Format SQL files using the syntaqlite formatter. Use when the user wants to format, reformat, or pretty-print SQL code. |
Format SQLite SQL using the syntaqlite CLI formatter.
# Format a file (print to stdout)
syntaqlite fmt query.sql
# Format in-place
syntaqlite fmt -i query.sql
# Format from stdin
echo "SELECT a,b FROM t WHERE x=1" | syntaqlite fmt
# Format multiple files via glob
syntaqlite fmt -i "**/*.sql"
# Format with options
syntaqlite fmt -w 120 -k upper query.sql
-e, --expression <SQL> — format an inline SQL expression instead of files-w, --line-width <N> — max line width (default: 80)-t, --indent-width <N> — spaces per indentation level (default: 2)-k, --keyword-case <upper|lower> — keyword casing (default: upper)-i, --in-place — overwrite files in place--check — check if files are formatted (exit 1 if not)--semicolons <true|false> — append semicolons (default: true)-i to write in place.-i.--check in CI to verify formatting without modifying files.Commit all current changes, push to a feature branch, and create a PR. Use when the user asks to commit, push, save progress, or ship changes.
Quickly commit and push current changes to a feature branch and create a PR, skipping pre-push checks. WARNING: if CI starts failing, use /cp instead.
Debug a SQL formatter bug. Use when the user reports incorrect formatting output — wrong whitespace, misplaced comments, blank lines, etc.
Parse SQL and inspect the AST using syntaqlite. Use when the user wants to see the parse tree, debug SQL syntax, or understand how a query is structured.
Validate SQL and report diagnostics using syntaqlite. Use when the user wants to check SQL for errors, lint SQL files, or verify correctness against a schema.
Run tests to verify correctness after code changes. Use when the user asks to run tests, verify changes, or check that things still work. Runs Rust unit tests and integration tests.