lint-and-validate

Automate multi-language linting and static analysis with per-language tools.

7|1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/skeletorflet/opencode-kit --skill lint-and-validate-skeletorflet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-and-validate
Source: https://github.com/skeletorflet/opencode-kit/tree/main/.opencode/skills/lint-and-validate
Command: npx skills add https://github.com/skeletorflet/opencode-kit --skill lint-and-validate-skeletorflet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automatically orchestrates quality control across multiple languages by applying the right linting and static analysis tools after code changes, reducing manual setup and accelerating feedback.

Core Features & Use Cases

  • Language-aware linting: auto-detects project language and selects appropriate tools (e.g., Ruff, MyPy, ESLint, TSC, go vet) to ensure code quality.
  • Cross-language workflow: coordinates per-language linters in a single run and reports results in a unified format.
  • Use cases: integrate into CI pipelines to enforce coding standards across Python, JavaScript/TypeScript, Go, Rust, Java, and C# projects.

Quick Start

Run the lint_runner on your project to start the multi-language linting workflow.

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 multi-language linting across Python, JavaScript, and Go projects?

Multi-language linting is automated by auto-detecting the project language and orchestrating per-language static analysis tools like Ruff, ESLint, and go vet in a single run to output structured results.

What is the best way to enforce coding standards across a polyglot CI pipeline?

Enforcing coding standards across a polyglot CI pipeline requires a unified static analysis workflow that coordinates per-language linters and reports results in a single structured format.

Can I run static analysis on Rust and C# code without manually configuring individual tools?

Static analysis on Rust and C# code runs without manual tool configuration by using language detection to automatically select and orchestrate the appropriate linters for each detected language.

Does this cross-language linting workflow support Java and TypeScript projects?

Cross-language linting supports Java and TypeScript projects by applying language-aware tooling such as TSC and Java static analysis tools within its unified quality control pipeline.

What are the limitations of using an automated language detection pipeline for code quality checks?

Automated language detection pipelines are limited to the major supported languages and depend on existing project structures, meaning unsupported languages or unconfigured environments will not be analyzed.