Automates linting, code formatting, and SQL query validation using project-defined Nix environments.
Install
mkdir -p .claude/skills/lint-kalbasit && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17538" && unzip -o skill.zip -d .claude/skills/lint-kalbasit && rm skill.zipInstalls to .claude/skills/lint-kalbasit
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Lint and format codeKey capabilities
- →Run standard linters with auto-fix
- →Format all files using Nix
- →Lint specific files
- →Lint SQL files
How it works
It executes `golangci-lint` to check code quality and apply fixes, then uses `nix fmt` for general file formatting. It also runs `sqlfluff lint` for SQL files.
Inputs & outputs
When to use lint
- →Lint project code
- →Format code files
- →Validate SQL queries
- →Auto-fix style issues
About this skill
// turbo-all
- Run standard linter (with fix enabled by default as preferred in CLAUDE.md):
nix develop --command golangci-lint run --fix
- (Optional) Run linter on specific files:
nix develop --command golangci-lint run --fix $FILE
- Format all files using Nix:
nix fmt
- (If SQL files modified) Lint SQL files:
nix develop --command sqlfluff lint db/query.*.sql db/migrations/
When not to use it
- →When the user wants to manually fix formatting issues
- →When the user wants to ignore code style guidelines
Limitations
- →Requires Nix for general file formatting
- →SQL linting only applies to specified paths
- →Relies on `golangci-lint` for standard linting
How it compares
This skill automates code quality checks and formatting across different file types, ensuring adherence to project standards without manual intervention.
Compared to similar skills
lint side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| lint (this skill) | 0 | 5mo | Review | Beginner |
| woocommerce-backend-dev | 7 | 2mo | No flags | Intermediate |
| property-based-testing | 1 | 1mo | No flags | Advanced |
| netalertx-code-standards | 1 | 2mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by kalbasit
View all by kalbasit →You might also like
woocommerce-backend-dev
woocommerce
Add or modify WooCommerce backend PHP code following project conventions. Use when creating new classes, methods, hooks, or modifying existing backend code. **MUST be invoked before writing any PHP unit tests.**
property-based-testing
trailofbits
Provides guidance for property-based testing across multiple languages and smart contracts. Use when writing tests, reviewing code with serialization/validation/parsing patterns, designing features, or when property-based testing would provide stronger coverage than example-based tests.
netalertx-code-standards
netalertx
NetAlertX coding standards and conventions. Use this when writing code, reviewing code, or implementing features.
review-implementation
karrioapi
Perform a fresh-context review of completed work against PRD, tests, and conventions.
test
FalkorDB
Run FalkorDB's test suites - Rust unit tests, Python e2e/function/MVCC/concurrency tests, openCypher TCK compliance tests, and flow tests. Use when asked to run, narrow down, or debug a failing test, or to decide which suite covers a change.
pida-code-review
Team-PIDA
Use when reviewing a PIDA branch, diff, or PR. Focus on bugs, regressions, missing tests, API contract drift, persistence risks, and operational issues before style comments.