Enforce consistent C code style for the ikigai project.
npx skills add https://github.com/mgreenly/ikigai --skill style
Please help me install this Agent Skill. Skill: style Source: https://github.com/mgreenly/ikigai/tree/main/.claude/library/style Command: npx skills add https://github.com/mgreenly/ikigai --skill style
Code style conventions for ikigai development to reduce inconsistencies and improve maintainability.
Apply these conventions when creating or reviewing ikigai C code to ensure consistency and maintainability.
High-intent search queries and answers about installing and using this skill.
Consistent C code style is enforced by standardizing include order to own headers, project headers, then system headers, and requiring fixed-width numeric types from inttypes.h to improve maintainability.
Avoiding static helper functions in C code improves testability by inlining code directly, which increases LCOV coverage metrics and ensures clear test boundaries without exposing internal linkage.
Standardizing C comment style requires using single-line comments exclusively and documenting the rationale behind decisions, reducing inconsistencies across core sources and test files.
Yes, these C coding style conventions apply to both core sources and tests, providing explicit rules for formatting, type usage, include order, and test readability across the entire project.
Enforcing coding style without external linting dependencies means all rules must be explicitly described in documentation and applied manually during code review, as there are no automated formatting components included.
openharmonyinsightSort C/C++ #include statements while preserving conditional compilation blocks and comments.
ProgrammerAnthonyAnalyze React and TypeScript code for structural quality and performance bottlenecks.
multicamEnforce C/C++ code style with inttypes.h types and Google-style include order.
kmt-tValidate C++ source code against defined naming and formatting rules.
