lint
Check for style and static analysis warnings using Deno lint
When & Why to Use This Skill
The Deno Lint skill is a specialized tool for maintaining high code quality and consistency in Deno projects. It automates the process of static analysis and style checking, identifying potential bugs, syntax issues, and deviations from best practices before code is executed or committed. By integrating the native Deno linting engine, it ensures that your codebase remains clean, readable, and compliant with industry standards.
Use Cases
- Pre-commit Quality Gates: Automatically run style and static analysis checks before committing code to ensure only compliant changes are added to the repository.
- Automated Pull Request Reviews: Streamline the code review process by using the skill to catch linting errors and style violations in PRs, allowing human reviewers to focus on logic.
- CI/CD Pipeline Integration: Incorporate automated linting into continuous integration workflows to prevent the deployment of code that fails quality standards.
- Refactoring and Modernization: Quickly scan and identify outdated patterns or style inconsistencies when updating legacy Deno projects to modern standards.
| name | lint |
|---|---|
| description | Check for style and static analysis warnings using Deno lint |
| license | MIT |
| compatibility | opencode |
| workflow | deno |
What I do
- Run
deno lintto check for style and static analysis warnings - Can also lint a single file using
deno lint <filename> - Uses the default Deno lint rules configured in
deno.jsonc - Catches potential issues and maintains code quality standards
When to use me
Use this when you want to verify code quality:
- Before committing changes
- Before creating a pull request
- After making significant code modifications
- As part of the CI/CD pipeline
Notes
- Customization of lint rules can be done in
deno.jsoncif necessary - This is part of the standard pre-commit workflow defined in
scripts/pre-commit.sh