lint

Run linters and static analysis tools with severity-based output and auto-fix mode.

3|1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/yon/agentic-dev-os --skill lint-yon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint
Source: https://github.com/yon/agentic-dev-os/tree/main/.claude/skills/lint
Command: npx skills add https://github.com/yon/agentic-dev-os --skill lint-yon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of running linters and static analysis tools on your codebase, ensuring consistent code quality and identifying potential issues early.

Core Features & Use Cases

  • Automated Linting: Runs make lint for the entire project or specific files/directories.
  • Severity Grouping: Organizes and reports issues by severity (Errors, Warnings, Info).
  • Auto-Fix Mode: Optionally attempts to automatically fix issues using make format and re-linting.
  • Use Case: Before committing code, run /lint to catch any style violations or potential bugs, ensuring your codebase adheres to project standards.

Quick Start

Run the lint skill to check all files in the project for code quality issues.

Frequently Asked Questions about lint

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

FAQPage Schema
How do I automate static analysis and code quality checks before a commit?

Automated static analysis runs linters across your code files to identify potential errors and style violations, catching quality issues and enforcing project code standards before you commit.

Can I run a linter on specific files instead of the entire project?

Yes, you can run a linter on targeted files and directories or execute project-wide static analysis, grouping the detected issues by severity for focused code review.

Is there an auto-fix mode for resolving code style violations?

Yes, an optional auto-fix mode attempts to automatically resolve code style violations by running formatting commands and then re-linting the files to verify the fixes.

How are reported linting errors organized for code review?

Linting errors are organized and reported by severity levels—Errors, Warnings, and Info—allowing you to prioritize critical code quality issues during review.

Do I need any external dependencies to run static analysis checks?

No external dependencies are required to run static analysis checks, as the skill directly executes linters and formatting tools already configured in your codebase.