new-cpp-lint

Design, test, and apply new C++ lint rules across the FastLED codebase.

7.5k|1.8k|Updated Nov 10, 2013
One-click install
npx skills add https://github.com/FastLED/FastLED --skill new-cpp-lint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-cpp-lint
Source: https://github.com/FastLED/FastLED/tree/main/.claude/skills/new-cpp-lint
Command: npx skills add https://github.com/FastLED/FastLED --skill new-cpp-lint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the process of creating, validating, and applying new C++ lint rules to ensure consistent coding standards across the FastLED project.

Core Features & Use Cases

  • Rule design: convert a description into a concrete lint rule and its tests.
  • Validation: build and run tests to verify rule behavior against representative code patterns.
  • Deployment: run the rule across the codebase (src/, platforms/, examples/, tests) and apply safe fixes when appropriate.

Quick Start

Run the new-cpp-lint workflow with a rule description to create, test, and apply a new C++ lint rule across the FastLED codebase.

Frequently Asked Questions about new-cpp-lint

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

FAQPage Schema
How do I create and enforce a new C++ lint rule across my codebase?

To enforce C++ lint rules, you design the checker from a description, build test suites for validation, run dry-runs against source directories, and apply safe fixes with suppressions for exceptions.

What is the best way to validate a custom C++ static analysis rule before deployment?

Validating a C++ static analysis rule requires building and running test suites to verify checker behavior against representative code patterns, ensuring accurate detection before applying fixes.

How do I apply lint rules to specific C++ project directories like src and tests?

Applying lint rules to C++ directories involves running the checker across src/, platforms/, examples/, and tests/ to identify violations and apply automated safe fixes where appropriate.

Can I suppress specific C++ lint rule violations for known exceptions?

Yes, suppression for known exceptions is supported during rule deployment, allowing specific code patterns to bypass the checker while enforcing the standard across the rest of the codebase.

Does this lint rule creation workflow handle both design and deployment?

Yes, the workflow handles rule design by converting descriptions into concrete checkers, and manages deployment by running the validated rules across the codebase to apply safe fixes.

Why do I need a test suite when adding a new C++ coding standard checker?

A test suite is needed to verify the checker correctly identifies target code patterns and avoids false positives, ensuring the new coding standard is enforced reliably before full deployment.