Parse ASan, UBSan, and TSan logs to identify memory errors and data races.
npx skills add https://github.com/mgreenly/ikigai --skill sanitizers
Please help me install this Agent Skill. Skill: sanitizers Source: https://github.com/mgreenly/ikigai/tree/main/.claude/library/sanitizers Command: npx skills add https://github.com/mgreenly/ikigai --skill sanitizers
Interpreting sanitizers' outputs (AddressSanitizer, UndefinedBehaviorSanitizer, and ThreadSanitizer) to pinpoint root causes of runtime errors and memory issues.
Run the sanitizer interpretation workflow against a log file to extract actionable insights.
High-intent search queries and answers about installing and using this skill.
AddressSanitizer logs are parsed to identify memory corruption by extracting structured error categories and actionable remediation guidance. This pinpoints runtime memory errors and provides escalation paths for CI pipeline failures or local debugging workflows.
The best way to triage ThreadSanitizer reports is running a log interpretation workflow that categorizes data races and provides structured remediation guidance. This extracts actionable insights directly from CI outputs to resolve concurrency issues quickly.
Yes, UndefinedBehaviorSanitizer output is parsed to identify null dereferences and other undefined behavior. The logs are categorized to provide specific remediation guidance for resolving these runtime errors during development or post-issue reviews.
Sanitizer logs get categorized by parsing ASan, UBSan, and TSan outputs into structured error types like memory corruption and data races. This categorization provides actionable fixes and escalation paths for quick triaging in development workflows.
No specific CI environment is required. Sanitizer log analysis is applicable to CI pipelines and local development workflows, requiring only a sanitizer log file to extract actionable insights and remediation guidance.
multicamInterpret ASan, UBSan, and TSan outputs to identify memory safety violations and data races.
wtthorntonDiagnose software bugs by analyzing error messages and stack traces.
rohanbhatia27Identifies memory corruption and undefined behavior in Ruby applications and C extensions via coverage-guided fuzzing and sanitizers.
StarRocksDiagnose StarRocks BE and FE node crashes, OOM, deadlocks, and Full GC pauses.
