style

Enforce C/C++ code style with inttypes.h types and Google-style include order.

Updated Mar 4, 2026

Search Tags:#testing #comments #code-style #c-cpp #include-order #inttypes #format-specifiers

Ready to run

npx skills add https://github.com/multicam/ikigai-rev --skill style-multicam

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: style
Source: https://github.com/multicam/ikigai-rev/tree/main/.claude-i/library/style
Command: npx skills add https://github.com/multicam/ikigai-rev --skill style-multicam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code style conventions and best practices for ikigai development, ensuring readable, consistent, and maintainable C/C++ code.

Core Features & Use Cases

Enforce clear comments that explain why something is done, not what.
Use explicit sized types from inttypes.h and appropriate format specifiers.
Apply a Google-style include order: own headers, project headers, then system headers.
Avoid static helper functions in implementation files; inline where appropriate.
Maintain consistent test code style to improve test reliability.

Quick Start

Apply these guidelines to a new or existing ikigai source file to enforce consistency.

Frequently Asked Questions about style

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

FAQPage Schema

What is the correct C++ include order for project headers and system headers?▼

The correct include order for C++ code is Google-style: own headers first, then project headers, followed by system headers. This structure improves readability and maintainability across the project.

How do I format explicit sized types in C/C++ using inttypes.h?▼

To format explicit sized types in C/C++, use types from inttypes.h and apply the corresponding printf and scanf format specifiers. Use size_t for object counts to ensure consistency.

Should I use static helper functions in C++ implementation files?▼

Avoid using static helper functions in C++ implementation files; inline them where appropriate instead. This prevents symbol collision and improves test code reliability.

How do I write effective code comments for maintainability?▼

Write effective code comments that explain why a specific implementation choice was made, not what the code does. This ensures the source remains readable and maintainable for future developers.

What are the C/C++ code style guidelines for test modules?▼

C/C++ test code style requires maintaining consistency across modules and files to improve test reliability. Apply explicit sized types and proper format specifiers to all test logic.