Enforce C/C++ code style with inttypes.h types and Google-style include order.
npx skills add https://github.com/multicam/ikigai-rev --skill style-multicam
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
Code style conventions and best practices for ikigai development, ensuring readable, consistent, and maintainable C/C++ code.
Apply these guidelines to a new or existing ikigai source file to enforce consistency.
High-intent search queries and answers about installing and using this skill.
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.
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.
Avoid using static helper functions in C++ implementation files; inline them where appropriate instead. This prevents symbol collision and improves test code reliability.
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.
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.
guan404mingCompile TVM FFI C++ projects from source using CMake.
macaughDetects injection, memory safety and authorization flaws in multiple languages.
nanorepublicaStandardize unit-test coding practices across Claude Code projects.
LeoKemp223Run cppcheck, clang-tidy, or GCC analyzer on C/C++ code for MISRA-C 2012 compliance.
