universal-quality-gate

Name: universal-quality-gate
Availability: InStock
Author: notque

Detect project languages via marker files and run configured linters and analyzers.

415|44|Updated Mar 18, 2026

Search Tags:#automation #quality #multi-language #pre-commit #static-analysis #lint

Ready to run

npx skills add https://github.com/notque/claude-code-toolkit --skill universal-quality-gate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: universal-quality-gate
Source: https://github.com/notque/claude-code-toolkit/tree/main/skills/universal-quality-gate
Command: npx skills add https://github.com/notque/claude-code-toolkit --skill universal-quality-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires quality_gate, and includes scripts (resource) components.

What problem does it solve?

Automates and enforces code quality across polyglot repositories by auto-detecting languages and applying the appropriate linters, formatters, and static analysis tools.

Core Features & Use Cases

Auto-detects languages via standard markers (e.g., go.mod, package.json, pyproject.toml) and runs language-specific quality checks.
Reports full tool output with file paths and line numbers, while gracefully degrading when tools are unavailable.
Supports pre-commit style checks and multi-language audits across large codebases.

Quick Start

Run the universal-quality-gate against your repository to perform a multi-language quality check.

Frequently Asked Questions about universal-quality-gate

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

FAQPage Schema

How do I run cross-language code quality checks in a multi-language repository?▼

Run cross-language code quality checks by auto-detecting project languages via marker files like go.mod and package.json, then applying language-specific linters and analyzers to enforce consistent quality across the repository.

Can I use pre-commit checks for multi-language static analysis?▼

Yes, you can use pre-commit checks for multi-language static analysis. The gate detects configured languages and executes the appropriate lint, format, and static analysis steps to ensure code quality before commits.

What happens if a linter or analyzer is unavailable during a repository audit?▼

If a linter or analyzer is unavailable during a repository audit, the quality gate gracefully degrades. It skips the missing tool and reports full output with file paths and line numbers for tools that are present.

How does the quality gate detect which languages are in my project?▼

The quality gate detects project languages by looking for standard marker files in the repository, such as go.mod for Go, package.json for JavaScript, and pyproject.toml for Python, to apply the correct linters.

Do I need to manually configure linters for each language in my project?▼

No, you do not need to manually configure linters. The quality gate relies on a language registry and the availability of configured tooling to automatically apply the correct lint, format, and static analysis steps based on detected marker files.

What's the best way to enforce consistent formatting across a polyglot codebase?▼

The best way to enforce consistent formatting across a polyglot codebase is to automate cross-language quality enforcement. This approach auto-detects languages and applies the appropriate language-specific formatters and analyzers.