lint-all

Run multiple static analysis tools and merge findings into one report.

3|1|Updated May 28, 2026
One-click install
npx skills add https://github.com/VMAFx/vmafx --skill lint-all
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-all
Source: https://github.com/VMAFx/vmafx/tree/main/.claude/skills/lint-all
Command: npx skills add https://github.com/VMAFx/vmafx --skill lint-all

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of running multiple code-quality tools separately by coordinating a single, repeatable lint pass and consolidating the results into one readable report.

Core Features & Use Cases

  • Parallel Quality Checks: Runs clang-tidy, cppcheck, include-what-you-use, ruff, and semgrep together to catch issues across C, C++, Python, and shell code.
  • Unified Reporting: Merges findings into a single severity-sorted report so developers can review all problems without switching between tools.
  • Targeted Fix Support: Applies safe auto-fixes for supported findings when requested, while preserving risky diagnostics for manual review.
  • Use Case: A maintainer preparing a release can run one workflow to validate the full codebase, inspect a consolidated report, and optionally auto-fix low-risk style issues before committing.

Quick Start

Ask the skill to run the full lint suite for the repository and produce a merged report, optionally restricting results to changed files or enabling safe fixes.

Frequently Asked Questions about lint-all

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

FAQPage Schema
How do I run multiple linters like clang-tidy, ruff, and semgrep in one pass?

Run multiple linters in one pass by using a unified workflow that executes clang-tidy, ruff, and semgrep in parallel, merging their findings into a single severity-sorted report for consistent code quality checks.

Can I consolidate static analysis findings from C, C++, and Python into a single report?

Yes, you can consolidate static analysis findings into a single report by merging results from clang-tidy, cppcheck, and ruff, allowing developers to review mixed-language repository issues without switching tools.

Does parallel static analysis require compile commands generation for C and C++ sources?

Yes, parallel static analysis requires compile commands generation to properly analyze C and C++ sources with clang-tidy, ensuring accurate detection of issues across the mixed-language repository during the unified lint workflow.

What is the best way to apply safe auto-fixes for linting errors without breaking risky code?

The best way to apply safe auto-fixes is through guarded behavior that targets only supported linter findings, preserving risky diagnostics for manual review while automatically resolving low-risk style issues when requested.

How do I filter static analysis results by severity after running a full codebase lint?

Filter static analysis results by severity after running a full codebase lint by reviewing the merged report, which automatically sorts findings by severity level to help prioritize code quality fixes.