lint-and-validate

Run linters, formatters, and type checkers on code changes before commits.

2|Updated May 8, 2026
One-click install
npx skills add https://github.com/xotong/claude-marketplace --skill lint-and-validate-xotong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-and-validate
Source: https://github.com/xotong/claude-marketplace/tree/main/plugins/code-quality/skills/lint-and-validate
Command: npx skills add https://github.com/xotong/claude-marketplace --skill lint-and-validate-xotong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of ensuring code quality by running linters, formatters, and type checkers before every commit, automatically fixing what is safe and reporting what still needs human attention.

Core Features & Use Cases

  • Auto-fix formatting across supported languages (Node.js, Python, Go, Ruby, Rust) before checks.
  • Run lint and type-check steps to surface remaining issues during pre-commit or PR workflows.
  • Use with common development pipelines to enforce consistent code quality before merges.

Quick Start

Install or configure pre-commit hooks to automatically run lint-and-validate in your project.

Frequently Asked Questions about lint-and-validate

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

FAQPage Schema
How do I automate pre-commit lint and type checks for multiple languages?

Automating pre-commit lint and type checks involves running linters, formatters, and type checkers on code changes. This Skill applies safe auto-fixes for formatting and reports remaining errors across Node.js, Python, Go, Ruby, and Rust.

Can I run formatting and lint checks before commits without including security scans?

Yes, you can run formatting and lint checks before commits while explicitly excluding security scans. This workflow automates language-specific tooling to enforce consistent code quality and surfaces issues during pre-commit or PR workflows.

What is the best way to enforce code quality in pull request CI gates?

The best way to enforce code quality in CI gates is using pre-commit hooks to run linters and type checkers. This process automatically fixes safe formatting issues and reports remaining errors before merges.

Does pre-commit formatting work across Node.js, Python, Go, Ruby, and Rust?

Pre-commit formatting works across Node.js, Python, Go, Ruby, and Rust. It automates safe auto-fixes for formatting changes before running lint and type-check steps to surface any remaining issues.

Why use pre-commit auto-fix formatting instead of only running linters?

Using pre-commit auto-fix formatting corrects safe style issues automatically, reducing manual effort. It then runs lint and type checks to surface remaining human attention requirements, ensuring consistent code quality before merges.