setup-lint-format-precommit

Configures linting and formatting tools with pre-commit hooks and CI enforcement.

9|3|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill setup-lint-format-precommit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-lint-format-precommit
Source: https://github.com/Sir-chawakorn/sanook-cli/tree/main/skills/setup-lint-format-precommit
Command: npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill setup-lint-format-precommit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates inconsistent code style, formatting churn, and broken commits by establishing a robust, automated toolchain that enforces standards locally and in CI.

Core Features & Use Cases

  • Automated Toolchain Setup: Configures Biome, ESLint/Prettier, or Ruff to handle linting and formatting without rule conflicts.
  • Pre-commit Gatekeeping: Implements fast, staged-only git hooks to prevent unformatted or lint-failing code from entering the repository.
  • CI Enforcement: Sets up non-fix, check-only CI gates that fail builds on drift, ensuring the codebase remains clean and compliant.

Quick Start

Run the setup-lint-format-precommit skill to configure the appropriate linting and formatting toolchain for this repository.

Frequently Asked Questions about setup-lint-format-precommit

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

FAQPage Schema
How do I set up pre-commit hooks for linting and formatting?

Pre-commit hooks for linting and formatting are set up by configuring staged-only git hooks that block unformatted or lint-failing code. This skill standardizes the toolchain locally to prevent style churn and broken commits from entering the repository.

What is the best way to enforce code quality in CI pipelines?

The best way to enforce code quality in CI pipelines is implementing non-fix, check-only CI gates that fail builds on formatting drift. This ensures zero-tolerance for linting warnings and keeps the codebase compliant.

Why does formatting drift happen and how do I prevent it?

Formatting drift happens when local editor settings bypass quality checks and allow inconsistent configurations. Prevent drift by coordinating local editor settings, git hooks, and CI pipeline configurations to enforce automated gatekeeping.

Can I use Biome, ESLint, or Ruff together without rule conflicts?

Yes, you can configure Biome, ESLint/Prettier, or Ruff without rule conflicts. This skill standardizes the linting and formatting workflows by integrating the appropriate toolchain to handle code quality without overlapping rules.

Do I need to run pre-commit hooks on all files or only staged changes?

Pre-commit hooks should run on staged changes only. This skill implements fast, staged-only git hooks to prevent unformatted or lint-failing code from entering the repository without slowing down development.