lint

Lint and format code across projects using project-specific configurations.

Updated May 25, 2026
One-click install
npx skills add https://github.com/cmetech/otto-cli --skill lint-cmetech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lint
Source: https://github.com/cmetech/otto-cli/tree/main/src/resources/skills/lint
Command: npx skills add https://github.com/cmetech/otto-cli --skill lint-cmetech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Linting and formatting are automated to enforce consistent code style, catch issues early, and reduce manual review effort.

Core Features & Use Cases

  • Auto-detects the project's linter and formatter (Biome, ESLint, and Prettier) and runs them with safe auto-fixes.
  • Lints changed files or a specified path, with optional --fix to apply fixes.
  • Works across multiple languages and integrates into CI, pre-commit hooks, or local development.

Quick Start

Lint the current project or a path using the default mode, then fix issues with --fix if needed.

Frequently Asked Questions about lint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I lint and format code automatically across different languages?▼

To lint and format code automatically, this tool detects your project's linter and formatter across JavaScript, TypeScript, Python, and Rust, applying safe auto-fixes to enforce consistent style and reduce drift.

Can I use auto-fix to format specific paths in my project?▼

Yes, you can format specific paths by passing directory or file arguments. By default it lints changed files, and you can append --fix to automatically apply safe formatting fixes to those specified paths.

Does this linting tool detect existing project configurations like Biome or ESLint?▼

Yes, the linting tool detects and uses existing project-specific configurations. It automatically recognizes setups for Biome, ESLint, Prettier, rustfmt, and Black, running them according to your predefined rules.

What is the best way to run a linter in CI pipelines and pre-commit hooks?▼

The best way to run a linter in CI and pre-commit hooks is using a tool that auto-detects project configurations and lints changed files. This integrates seamlessly into your pipelines to catch issues early and reduce manual review.

Why should I auto-format code in local development instead of just during CI?▼

You should auto-format code in local development to catch issues early and reduce drift before committing. Running it locally alongside CI and pre-commit hooks ensures consistent code style across the entire development lifecycle.