race-conditions

To detect race conditions and TOCTOU vulnerabilities, this Skill orchestrates static analysis checks and language-specific detectors to identify high-risk code areas with unsynchronized access. It aggregates these scanner findings to highlight timing-dependent failures across async boundaries.

Auditing for shared state bugs and concurrency issues involves a guided workflow: identifying high-risk files, running available scanners, and performing manual code analysis. This approach detects check-then-act pitfalls and generates a structured findings report.

To remediate TOCTOU and check-then-act pitfalls, this Skill provides guided remediation by suggesting concrete fixes and safeguard recommendations. These mitigations directly address unsynchronized access and shared-state bugs that lead to data corruption.

Yes, static analysis can find flaky behavior caused by shared state across async boundaries. The Skill coordinates language-specific race detectors to highlight unsynchronized access and timing-dependent failures that are difficult to reproduce in standard tests.

Race condition detection works without complex environment dependencies. The Skill operates with zero dependencies, analyzing source code directly to identify concurrency issues and format findings for integration without requiring external setup.

Automated concurrency analysis catches subtle timing-dependent failures that manual code review often misses. By orchestrating static analysis scanners, it effectively identifies high-risk TOCTOU patterns and unsynchronized access across large codebases to prevent data corruption.