lint

Configure linters, formatters, pre-commit hooks, and CI enforcement across repositories.

26|8|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/arbazkhan971/godmode --skill lint-arbazkhan971
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint
Source: https://github.com/arbazkhan971/godmode/tree/main/skills/lint
Command: npx skills add https://github.com/arbazkhan971/godmode --skill lint-arbazkhan971

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces consistent formatting and linting across a codebase to eliminate style debates, reduce CI failures, and catch preventable errors before review.

Core Features & Use Cases

  • Auto-detection and assessment of existing linters, formatters, editorconfig, and pre-commit hooks to produce a remediation plan.
  • Tool selection and configuration for ESLint/Biome, Prettier, Ruff, golangci-lint, and Husky/pre-commit with staged-file fixes and CI enforcement.
  • Auto-fix strategy and safety including layered fixes, staged pre-commit checks, CI zero-warnings enforcement, and rollback when fixes break tests.
  • Use case: Convert a legacy mixed-style repository to a single, automated lint+format pipeline, install pre-commit hooks, and enforce --max-warnings=0 in CI.

Quick Start

Run the lint skill to detect and auto-fix lintable issues, install pre-commit hooks, and configure CI to enforce zero warnings.

Frequently Asked Questions about lint

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

FAQPage Schema
How do I enforce consistent code style and automatically fix linting violations in my repository?

You can enforce consistent code style by running an automated lint and format pipeline that detects existing configurations, applies layered auto-fixes, and sets up pre-commit hooks to prevent unstyled code from being committed.

What's the best way to configure ESLint and Prettier to avoid formatting conflicts?

Configuring ESLint and Prettier together requires a layered auto-fix strategy where the formatter runs first, followed by the linter, ensuring both tools are installed correctly to prevent overlapping style rules from causing CI failures.

Does automated linting support Python and Go projects or just JavaScript?

Automated linting supports JavaScript, TypeScript, Python, Go, Rust, and Ruby projects by configuring language-specific linters like Ruff and golangci-lint alongside formatters to enforce consistent styling across mixed-language repositories.

How do pre-commit hooks stop linting errors from reaching CI?

Pre-commit hooks stop linting errors by running staged-file checks before a commit is finalized, automatically fixing violations locally and enforcing zero warnings so preventable style errors never trigger remote CI failures.

What happens if an automated lint auto-fix breaks my existing tests?

If an auto-fix breaks existing tests, the lint pipeline provides a test-preserving rollback mechanism to revert the problematic changes, ensuring automated style corrections do not introduce functional regressions into your codebase.

How do I enforce zero warnings in CI for linting violations?

To enforce zero warnings in CI, you configure your lint pipeline to run with the --max-warnings=0 flag, causing the CI step to fail immediately if any linting violations are detected in the pushed code.