linting

Check and fix Megahub source files with clang-format, cppcheck, Prettier, and ESLint.

5|2|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/mirkosertic/Megahub --skill linting-mirkosertic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linting
Source: https://github.com/mirkosertic/Megahub/tree/main/.claude/skills/linting
Command: npx skills add https://github.com/mirkosertic/Megahub --skill linting-mirkosertic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you apply the correct formatting and linting checks for Megahub so code stays consistent, reviewable, and easier to maintain across C++ and frontend files.

Core Features & Use Cases

  • C++ formatting and analysis: Use clang-format and cppcheck to keep firmware and library code aligned with project style and catch common issues.
  • Frontend quality checks: Use Prettier and ESLint to format and validate JavaScript and CSS in the web IDE.
  • Pre-commit enforcement: Rely on lefthook to automatically run the right checks on staged files before commits land.
  • Use case: After editing a firmware module or changing the IDE UI, apply the repository's formatting rules and run the relevant lint checks before opening a pull request.

Quick Start

Ask for the correct Megahub formatting or linting steps for the files you changed and apply the repository's recommended checks before you commit.

Frequently Asked Questions about linting

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

FAQPage Schema
How do I run linting and formatting checks on changed C++ firmware files?

To run linting and formatting on changed C++ firmware files, apply the repository's clang-format style rules and execute cppcheck static analysis to validate code and catch common issues before committing.

Can I use ESLint v9 and Prettier to format frontend JavaScript and CSS?

Yes, you can use ESLint v9 and Prettier to format and validate frontend JavaScript and CSS by applying the repository's configured web IDE formatting rules to maintain code quality and consistency.

What's the best way to enforce pre-commit linting checks on staged files?

The best way to enforce pre-commit linting on staged files is using lefthook to automatically run the correct formatting and static analysis checks before commits land in the repository.

Does lefthook support running clang-format and cppcheck together for C++ code?

Yes, lefthook supports running clang-format and cppcheck together by validating staged C++ firmware and library code against repository style configurations to ensure consistent formatting and issue detection.

Why does my Megahub code fail formatting checks before a pull request?

Your Megahub code fails formatting checks because it has not been validated against the repository's clang-format, Prettier, or ESLint rules, which must be applied to changed files before opening a pull request.

When do I need to run linting checks on web IDE JavaScript changes?

You need to run linting checks on web IDE JavaScript changes whenever you modify the IDE UI, ensuring Prettier and ESLint validate formatting and style before you commit the code.