quality-checker

To perform static analysis and memory safety checks before pushing code changes, run the quality-checker skill to execute cppcheck, shellcheck, and valgrind automatically. It validates code changes comprehensively to ensure code quality and prevent debugging issues in your repository.

The best way to detect race conditions and deadlocks in multi-threaded applications is using thread safety checks via helgrind. The quality-checker skill automates this helgrind analysis to identify concurrency issues and validate your multi-threaded code changes before repository submission.

Yes, you can use the quality checker for build verification. It compiles your source code with strict warnings and checks binary artifacts, ensuring that potential build issues are caught and resolved before you commit your changes to the repository.

No external dependencies are required to run the quality checker skill itself. It orchestrates existing analysis tools like cppcheck, shellcheck, valgrind, and helgrind through its internal scripts to deliver comprehensive code validation without needing additional setup.

You need to run memory leak detection with valgrind when validating code changes or debugging memory safety issues before a repository push. The quality checker skill streamlines this valgrind execution to identify leaks and ensure code quality prior to committing.

Code quality verification is the process of running static analysis, memory safety, thread safety, and build verification checks. It prevents repository issues by catching potential bugs, leaks, and race conditions early, ensuring only validated code changes are pushed.