style-check

Check modified C++ and header files for style violations using astyle and git diff.

17|6|Updated Oct 27, 2025
One-click install
npx skills add https://github.com/fossuav/aap --skill style-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: style-check
Source: https://github.com/fossuav/aap/tree/main/claude/skills/style-check
Command: npx skills add https://github.com/fossuav/aap --skill style-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires astyle, git, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the verification of code style and formatting for C++ files, ensuring adherence to ArduPilot's development standards before committing changes.

Core Features & Use Cases

  • Automated Style Checking: Uses astyle and git diff to check for trailing whitespace and formatting violations.
  • Targeted Checks: Focuses only on modified files to ensure efficiency.
  • Use Case: Before committing a code change, run this skill to automatically catch any formatting errors, preventing style-related commit rejections.

Quick Start

Run the style-check skill to verify the formatting of all modified C++ and header files in the current repository.

Frequently Asked Questions about style-check

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

FAQPage Schema
How do I check C++ code style and formatting before a git commit?

To check C++ code style before a commit, use the style-check skill to automatically verify modified files using astyle and git diff. It specifically targets changed C++ and header files to efficiently catch formatting violations and trailing whitespace.

Why does my ArduPilot code change get rejected for formatting violations?

ArduPilot code changes get rejected for formatting violations when modified C++ files do not adhere to project-specific coding standards. Running an automated style check identifies issues with indentation, line endings, brace placement, and whitespace before submission.

Do I need astyle installed to check formatting in my modified C++ files?

Yes, you need astyle installed because the style-check skill relies on it as a core dependency to verify code style and formatting. It also requires git to determine which C++ and header files have been modified.

Can I run code style checks on only the modified files in my repository?

Yes, you can run code style checks on only modified files by using astyle combined with git diff. This targeted approach ensures efficient verification by applying formatting rules exclusively to changed C++ and header files.

What is the best way to automate C++ formatting checks for ArduPilot development?

The best way to automate C++ formatting checks for ArduPilot is to use a targeted skill that runs astyle against git diff output. This ensures compliance with project-specific rules for indentation, line endings, and brace placement before committing.