quality
Quality skill for the ikigai project
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Quality
Description
Testing and quality requirements for development phase. Focus on high coverage.
Pre-Commit Requirements
Before creating commits:
-
make fmt- Format code -
make check- All tests pass -
make lint- Complexity/file size checks pass
Test Execution
By Default: Tests run in parallel, with 24 parallel tests on this machine.
-
MAKE_JOBS=24- up to 24 concurrent tests
When you need clear debug output (serialize execution):
PARALLEL=0 MAKE_JOBS=1 make check
Best practice: Test individual files during development, run full suite before commits.
Example:
make build/tests/unit/array/basic_test && ./build/tests/unit/array/basic_test
Build Modes
make BUILD={debug|release|sanitize|tsan|coverage}
-
debug- Development builds with symbols -
release- Optimized production builds -
sanitize- Address and undefined behavior sanitizers -
tsan- Thread sanitizer -
coverage- Code coverage analysis
Development Phase Focus
- Aim for high test coverage of new code
- Test the happy path and obvious error cases
- Coverage gaps will be closed in a dedicated coverage phase
- Don't let coverage metrics slow down feature development
CRITICAL: Never run multiple make commands simultaneously. Different targets use incompatible compiler flags and will corrupt the build.
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-01-26
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!