lint-gate

Halts task completion when lint or type errors are detected in codebase.

6|Updated Mar 11, 2026

Search Tags:#linting #code-quality #static-analysis #ci-cd #development-tools #typechecking

Ready to run

npx skills add https://github.com/open-hax/opencode-skills --skill lint-gate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lint-gate
Source: https://github.com/open-hax/opencode-skills/tree/main/.opencode/skills/lint-gate
Command: npx skills add https://github.com/open-hax/opencode-skills --skill lint-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents tasks from being marked complete when lint or type errors remain, ensuring code quality before delivery.

Core Features & Use Cases

LSP Diagnostics: run diagnostics on modified files to surface lint/type issues early.
Type Checking: perform workspace type checks to catch type errors across the codebase.
Linting: apply lint rules to enforce style and correctness, with guidance to fix root causes.
Use Case: before closing a sprint, run the gate to guarantee a clean merge ready state.

Quick Start

Run the lint gate after edits to verify there are no lint or type errors before marking work complete.

Frequently Asked Questions about lint-gate

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

FAQPage Schema

How do I prevent task completion when lint or type errors are detected in the codebase?▼

To prevent task completion with lint or type errors, use a lint gate to halt closure until LSP diagnostics, type checks, and lint rules pass on modified files. This strictly enforces code quality before delivery.

How do I enforce lint and type correctness before a sprint merge?▼

Enforce lint and type correctness before a sprint merge by running a lint gate across the workspace to surface LSP diagnostics and type errors. This guarantees a clean, merge-ready state by blocking incomplete tasks.

What is the correct sequence to run static analysis and type checking during local development?▼

The correct sequence for static analysis and type checking is to run LSP diagnostics on modified files first, then perform workspace type checks, and finally apply lint rules to fix root causes before completion.

Can I use a lint gate in CI pipelines and code reviews to enforce code quality?▼

Yes, you can use a lint gate in CI pipelines and code reviews to enforce code quality across changes. It halts task completion when lint or type errors are detected, ensuring strict correctness before delivery.

Why does my task fail to complete when workspace type checks catch errors?▼

Your task fails to complete because the lint gate enforces a strict sequence: LSP diagnostics, type checks, and lint must pass. It halts completion to force you to fix root causes of type errors before delivery.

Does the lint gate fix root causes of lint errors automatically?▼

No, the lint gate does not automatically fix errors. It applies lint rules to enforce style and correctness and provides guidance to help you manually fix the root causes of lint and type errors before completion.