Verify Command - Comprehensive Validation

Verify code quality, syntax, and security across multiple programming languages.

3|1|Updated Apr 18, 2021

Search Tags:#code quality #code review #linting #security #CI/CD #verification

Ready to run

npx skills add https://github.com/nashgao/mqtt-client --skill verify-command-comprehensive-validation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Verify Command - Comprehensive Validation
Source: https://github.com/nashgao/mqtt-client/tree/main/.claude/skills/quality/verify
Command: npx skills add https://github.com/nashgao/mqtt-client --skill verify-command-comprehensive-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of verifying code quality, syntax, standards compliance, and security across various programming languages and file types, ensuring a robust and maintainable codebase.

Core Features & Use Cases

Multi-language Support: Verifies code written in JavaScript, TypeScript, Python, Go, Rust, Java, C/C++, C#, PHP, CSS, HTML, JSON, YAML, Markdown, Shell, SQL, and Dockerfiles.
Comprehensive Checks: Includes syntax validation, linting, static analysis, security vulnerability scanning, and dependency checks.
Configurable Modes: Supports 'comprehensive', 'quick', 'syntax-only', 'security-only', 'style-only', and 'dependencies-only' verification.
Use Case: Before merging a pull request, run claude verify --comprehensive to catch any potential bugs, style violations, or security risks across the entire project.

Quick Start

Run the verify command to check the quality of your code.

Frequently Asked Questions about Verify Command - Comprehensive Validation

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

FAQPage Schema

How do I run comprehensive code quality and security checks before a pull request?▼

To run comprehensive code quality and security checks before a pull request, execute a verification command supporting multiple languages to analyze syntax, linting, static analysis, and dependency vulnerabilities across the entire project.

Can I scan only for security vulnerabilities without checking code style?▼

Yes, you can scan only for security vulnerabilities by using configurable verification modes. Select the security-only mode to target potential vulnerabilities while skipping syntax validation and style compliance checks.

Does multi-language static analysis work for TypeScript, Go, and Rust in the same project?▼

Multi-language static analysis works for TypeScript, Go, and Rust in the same project. The verification process analyzes syntax, standards compliance, and security across JavaScript, TypeScript, Python, Go, Rust, Java, C/C++, and more.

What is the best way to automate linting and dependency checks across multiple file types?▼

The best way to automate linting and dependency checks across multiple file types is configuring a comprehensive verification mode. This integrates static analysis, security scanning, and dependency checks for YAML, Dockerfiles, SQL, and various programming languages.

Why does my CI/CD pipeline need syntax validation for Dockerfiles and Shell scripts?▼

Your CI/CD pipeline needs syntax validation for Dockerfiles and Shell scripts to ensure a robust and maintainable codebase. Automated syntax verification catches configuration errors and compliance issues before deployment.

When should I use quick mode versus comprehensive mode for code verification?▼

Use quick mode for rapid feedback during active development, and comprehensive mode before merging a pull request. Comprehensive mode performs deep static analysis and security vulnerability scanning, while quick mode skips extensive checks.