SQLFormat
Format, lint, and pretty-print SQL with dialect conversion. Use when checking style, validating syntax, formatting queries, generating clean SQL.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/bytesagain3/sqlformatSQLFormat
SQL query formatter, linter, and devtools toolkit. Check SQL style, validate syntax, format and pretty-print queries, lint for best practices, explain execution plans, convert between dialects, and manage SQL templates — all from the command line.
Commands
Run sqlformat <command> [args] to use. Each command records timestamped entries to its own log file.
Core Operations
| Command | Description |
|---|---|
check <input> | Check SQL code for style or correctness issues |
validate <input> | Validate SQL syntax against rules |
generate <input> | Generate formatted SQL snippets or boilerplate |
format <input> | Format and pretty-print a SQL query with proper indentation |
lint <input> | Lint SQL for style violations and anti-patterns |
explain <input> | Record query explanation or execution plan notes |
convert <input> | Convert SQL between dialects (MySQL ↔ PostgreSQL, etc.) |
template <input> | Store or retrieve reusable SQL templates |
diff <input> | Record differences between SQL versions |
preview <input> | Preview a formatting transformation before applying |
fix <input> | Log an applied fix to a SQL issue |
report <input> | Record a formatting or lint report |
Utility Commands
| Command | Description |
|---|---|
stats | Show summary statistics across all log files (entry counts, disk usage) |
export <fmt> | Export all data in a given format: json, csv, or txt |
search <term> | Search across all log files for a keyword (case-insensitive) |
recent | Display the last 20 lines from the activity history log |
status | Health check — version, data dir, entry count, disk usage |
help | Show the full command reference |
version | Print current version (v2.0.0) |
Note: Each core command works in two modes — call with no arguments to view recent entries (last 20), or pass input to record a new timestamped entry.
Data Storage
All data is stored locally in plain-text log files:
~/.local/share/sqlformat/
├── check.log # Style check records
├── validate.log # Syntax validation results
├── generate.log # Generated SQL snippets
├── format.log # Formatted query records
├── lint.log # Lint findings
├── explain.log # Execution plan notes
├── convert.log # Dialect conversion records
├── template.log # Reusable SQL templates
├── diff.log # SQL version diffs
├── preview.log # Preview entries
├── fix.log # Applied fix records
├── report.log # Lint/format reports
└── history.log # Unified activity log (all commands)
Each entry is stored as YYYY-MM-DD HH:MM|<input> (pipe-delimited). The history.log file receives a line for every command executed, providing a single timeline of all activity.
Requirements
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-bytesagain3-sqlformat": {
"enabled": true,
"auto_update": true
}
}
}Tags
Related Skills
Epoch
Convert Unix timestamps, compare epochs, and do time arithmetic. Use when converting dates, debugging timestamps, or checking timezone offsets.
vibe-coding-checker
描述一个功能或项目，AI 快速评估用 Cursor/Windsurf/Bolt 等 AI 编程工具能否独立实现， 给出可行性判断、推荐工具、拆解路径和风险提示。
Dotfiles
Backup, sync, and version-track dotfiles across multiple machines. Use when syncing configs, backing up settings, restoring on new machines.
UnixTime
Convert Unix timestamps to dates and back. Use when parsing epoch values, calculating time differences, debugging logs, or generating relative dates.
JSONLint
Validate and pretty-print JSON files from the terminal. Use when linting config files, formatting API payloads, checking syntax before deployment.