rt.safety.auditor

Real-time safety violations in C++ audio code occur when heap allocations, locks, blocking I/O, or unbounded loops execute in audio threads like processBlock or audioCallback. Auditing scans these paths to flag unsafe patterns and provides line-by-line reports with actionable fixes to ensure deterministic, dropout-free execution.

Heap allocations, mutex locks, blocking I/O operations, and unbounded loops are forbidden in real-time audio threads because they introduce unpredictable latency and timing jitter. This skill detects `new` calls, `std::mutex` usage, `std::cout` statements, and similar patterns that violate real-time constraints.

Yes, you can audit individual C++ files or specific file patterns within your codebase. The skill scans processBlock, audioCallback, render paths, and related real-time code sections, generating detailed markdown reports that identify violations and explain their performance impact.

Real-time constraints prevent audio dropouts, latency spikes, and glitches that degrade playback quality. Enforcing sample-accurate timing, deterministic execution, and safe memory management using 64-bit atomic counters keeps your audio engine broadcast-safe and reliable under performance pressure.

Automated static analysis detects real-time violations before code reaches production. This skill applies domain-specific knowledge to identify unsafe patterns early in development, guiding you toward safe, performant implementations that maintain consistent audio thread execution.

Manual review is error-prone and time-consuming. Automated auditing catches heap allocations, locks, and blocking operations systematically across your C++ audio codebase, reducing the risk of subtle real-time violations that would only surface during performance testing or live playback.