/lint

> Run linters and formatters, report issues, auto-fix where possible.

170 stars

byMiosa-osa

View on GitHub Installation ↓

Best use case

/lint is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

> Run linters and formatters, report issues, auto-fix where possible.

Teams using /lint should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/lint/SKILL.md --create-dirs "https://raw.githubusercontent.com/Miosa-osa/canopy/main/library/skills/development/lint/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/lint/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How /lint Compares

Feature / Agent	/lint	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

> Run linters and formatters, report issues, auto-fix where possible.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# /lint

> Run linters and formatters, report issues, auto-fix where possible.

## Usage
```
/lint [path] [--fix] [--strict] [--format <format>]
```

## What It Does
Detects the project language and runs appropriate linters and formatters. Reports style violations, potential bugs, and security issues. With `--fix`, auto-corrects fixable issues.

## Implementation
1. **Detect project type** and available linters.
2. **Run linters** in order:
   - Elixir: `mix format --check-formatted` + `mix credo --strict`
   - TypeScript/JS: `eslint` + `prettier --check`
   - Go: `golangci-lint run`
   - Python: `ruff check` + `black --check`
   - Rust: `cargo clippy`
3. **Parse output** -- extract file, line, rule, severity, message.
4. **Auto-fix** (if `--fix`) -- run formatters and auto-fixable rules.
5. **Report** -- categorized by severity (error, warning, info).

## Examples
```bash
# Check for lint issues
/lint

# Auto-fix all fixable issues
/lint --fix

# Strict mode (warnings become errors)
/lint --strict

# Lint specific directory
/lint lib/optimal_engine/
```

## Command