lint

Lint and format code across languages with Git integration.

7|3|Updated Jul 31, 2025

Search Tags:#automation #git #commit #code-quality #lint #format

Ready to run

npx skills add https://github.com/seabbs/claude-code-config --skill lint-seabbs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lint
Source: https://github.com/seabbs/claude-code-config/tree/main/skills/lint
Command: npx skills add https://github.com/seabbs/claude-code-config --skill lint-seabbs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Linting and formatting are automated to enforce code style across projects, reducing review time and defects.

Core Features & Use Cases

Lint multiple languages with appropriate tools and checks (style, whitespace, and structural issues)
Auto-format code and optionally stage a commit with a standardized message
Support different scopes (commit, pr, all) to control how aggressively fixes are applied

Quick Start

Run lint with the default scope to quickly clean up a repository, then review and commit as needed.

Frequently Asked Questions about lint

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

FAQPage Schema

How do I automate code formatting and linting before a git commit?▼

To automate code formatting and linting before a git commit, you can run the lint skill to apply style constraints and optionally stage a standardized commit message with the fixes.

Can I run linters across multiple languages in one pass?▼

Yes, you can run linters across multiple languages in one pass by executing the skill, which applies language-specific linters and formatters to validate whitespace and structural issues.

How do I control the scope of automated code quality fixes?▼

You control the scope of automated code quality fixes by specifying a scope parameter such as commit, pr, or all, which determines how aggressively the tool applies formatting and linting fixes.

What is the best way to enforce code style constraints in a repository?▼

The best way to enforce code style constraints in a repository is using automated linting and formatting tools that validate style rules and generate a report of issues fixed and remaining checks.

Do I need external data sources to lint and format my codebase?▼

No, you do not need external data sources to lint and format your codebase because the skill requires no external data and operates directly on your local code files within Git workflows.