universal-quality-gate

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.

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.

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.

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.

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.

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.