sql-migration-linterLint .sql migration files for common mistakes — missing IF EXISTS guards, UPDATE/DELETE without WHERE, non-idempotent CREATE, missing transaction wrappers, r...
Install via ClawdBot CLI:
clawdbot install charlie-morrison/sql-migration-linterGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Oct 2, 2026
A platform team integrates the linter into GitHub Actions to block pull requests containing unsafe SQL migrations. It runs on every commit touching the migrations/ directory with exit-code gating, so UPDATE/DELETE without WHERE and missing transactions never reach staging.
A small engineering team uses a pre-commit hook to lint migration files locally before they are staged. Developers get instant feedback on missing IF NOT EXISTS guards and mixed indentation, reducing review churn.
A fintech company runs the linter with --dialect postgres across all migration files to catch CREATE INDEX without CONCURRENTLY and ADD COLUMN NOT NULL without DEFAULT. The findings feed a quarterly database reliability report.
A consultancy onboarding a legacy codebase runs the linter against thousands of existing SQL migration files to inventory risky patterns like DROP TABLE without IF EXISTS and TRUNCATE. Results are summarized in JSON for a client remediation roadmap.
A coding bootcamp adds the linter to its project templates so students learn safe migration practices early. Instructors use the summary output to highlight common mistakes across the cohort.
The CLI remains free and open-source, while a paid cloud dashboard aggregates lint results across repositories, tracks trends, and sends Slack alerts on new violations. Teams pay per seat or per repository.
A paid enterprise edition bundles the linter with policy packs, custom rule authoring, audit logs, and SSO. It targets regulated industries that must prove database change controls.
Agencies and consultants use the linter as a diagnostic tool for paid database modernization audits. Deliverables include prioritized remediation reports and migration rewrites.
💬 Integration Tip
Drop the script into a pre-commit hook or CI step with --min-severity warning for PR gates and exit code checks. Use --dialect postgres and --format json to unlock Postgres rules and pipe structured results into dashboards or GitHub Actions annotations.
Scored Oct 2, 2026
Control desktop applications on Windows — launch, close, focus, resize, move windows, simulate keyboard/mouse input, manage processes, control VSCode, read clipboard, and capture screen info. Use when the user wants to interact with any running program, switch windows, type text, press shortcuts, open files in VSCode, manage running processes, or get system display information.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Pragmatic coding standards for writing clean, maintainable code — naming, functions, structure, anti-patterns, and pre-edit safety checks. Use when writing new code, refactoring existing code, reviewing code quality, or establishing coding standards.
Claude Code integration for OpenClaw. This skill provides interfaces to: - Query Claude Code documentation from https://code.claude.com/docs - Manage subagents and coding tasks - Execute AI-assisted coding workflows - Access best practices and common workflows Use this skill when users want to: - Get help with coding tasks - Query Claude Code documentation - Manage AI-assisted development workflows - Execute complex programming tasks
Plan, draft, version, and refine written content with enforced versioning and quality audits.
Use when writing tests, creating test strategies, or building automation frameworks. Invoke for unit tests, integration tests, E2E, coverage analysis, performance testing, security testing.