quality-code-check

Lints, type-checks, and verifies builds across five programming languages.

1|Updated Oct 30, 2025

Search Tags:#linting #build #quality #lint #ci #type-check

Ready to run

npx skills add https://github.com/phananhtuan09/ai-agent-workflow --skill quality-code-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: quality-code-check
Source: https://github.com/phananhtuan09/ai-agent-workflow/tree/main/.opencode/skill/quality-code-check
Command: npx skills add https://github.com/phananhtuan09/ai-agent-workflow --skill quality-code-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establish consistent code quality standards through automated validation tools, ensuring code reliability, maintainability, and consistency across languages.

Core Features & Use Cases

Linting across languages (JavaScript/TypeScript, Python, Go, Rust, Java) to enforce style and catch issues early
Type checking across languages to ensure type safety and compatibility
Build verification to confirm compilability and proper packaging before deployment
Use Case: Integrate into CI or pre-commit to validate changes and prevent buggy code from entering main branches

Quick Start

Run automated quality checks on your changed code to lint, type-check, and verify builds across supported languages.

Frequently Asked Questions about quality-code-check

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

FAQPage Schema

How do I automate multi-language code quality checks in my CI pipeline?▼

Multi-language code quality validation automates linting, type-checking, and build verification across JavaScript/TypeScript, Python, Go, Rust, and Java projects. It runs during development, before PRs, and within CI to enforce consistent quality standards and prevent buggy code from entering main branches.

Can I run ESLint and golangci-lint together for cross-language linting?▼

Yes, cross-language linting integrates ESLint for JavaScript/TypeScript, Ruff/MyPy for Python, golangci-lint for Go, Clippy for Rust, and Maven/Gradle for Java. The tooling uses project configuration to detect and run the applicable toolchain for each specific language.

What is the best way to enforce type checking across multiple programming languages?▼

Type checking across languages ensures type safety by running language-specific validators like MyPy for Python and TypeScript's built-in checker. This automated validation confirms type compatibility and catches issues early before changes are merged into main branches.

Does this code validation tool work with Rust Clippy and Maven build verification?▼

Yes, code validation supports Rust Clippy and Maven/Gradle build verifications. The automation uses project configuration to detect the correct toolchain, confirming compilability and proper packaging across JavaScript/TypeScript, Python, Go, Rust, and Java projects before deployment.

Do I need to configure multiple linters manually to validate builds before deployment?▼

No manual configuration of multiple linters is needed, as build verification uses your existing project configuration to determine the applicable toolchain. This automates language-specific validations across supported languages to confirm compilability and proper packaging before deployment.

Why should I run automated quality checks before creating a pull request?▼

Running automated quality checks before a pull request prevents buggy code from entering main branches by validating changes early. Pre-commit validation enforces style consistency, ensures type safety, and verifies builds across all supported languages before code review.