review-reentrancy

Audit COM, DWM, and Win32 API calls for STA message pump reentrancy hazards.

1|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/cwilliams5/Alt-Tabby --skill review-reentrancy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-reentrancy
Source: https://github.com/cwilliams5/Alt-Tabby/tree/main/.claude/skills/review-reentrancy
Command: npx skills add https://github.com/cwilliams5/Alt-Tabby --skill review-reentrancy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies and mitigates critical reentrancy bugs in the paint and frame loop paths of an application, which can lead to subtle and hard-to-diagnose issues like partial renders, frozen paints, and corrupted state.

Core Features & Use Cases

  • COM Call Auditing: Systematically reviews all COM, DWM, and Win32 API calls within critical rendering paths.
  • Reentrancy Hazard Identification: Pinpoints potential issues where COM's STA message pump can dispatch callbacks mid-execution, even when Critical "On" is active.
  • Invariant Verification: Ensures five key invariants are met to prevent reentrancy-related failures.
  • Use Case: A developer can use this Skill to perform a high-consequence security and stability review on a graphics-intensive application's rendering pipeline before release, ensuring a robust user experience.

Quick Start

Initiate a planning mode to audit all COM/DWM/Win32 calls in the paint and frame loop paths for STA message pump reentrancy hazards.

Frequently Asked Questions about review-reentrancy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit COM calls for STA message pump reentrancy hazards?

To audit COM calls for STA message pump reentrancy hazards, systematically review all COM, DWM, and Win32 API calls within application paint and frame loop paths to identify blocking calls that dispatch timer or hotkey callbacks mid-execution.

Why does my rendering pipeline experience partial renders or frozen paints during COM calls?

Partial renders or frozen paints during COM calls occur because the STA message pump can dispatch callbacks mid-execution, even when Critical "On" is active, leading to reentrancy bugs and corrupted application state within the rendering pipeline.

What invariants do I need to verify to prevent reentrancy bugs in Win32 API calls?

To prevent reentrancy bugs in Win32 API calls, verify that five critical invariants are met to maintain thread safety and predictable rendering behavior, ensuring blocking COM calls do not disrupt the application paint and frame loop paths.

Can I use this COM auditing approach for graphics-intensive applications before release?

Yes, you can use this COM auditing approach to perform a high-consequence security and stability review on a graphics-intensive application's rendering pipeline before release, ensuring a robust user experience by verifying thread safety and preventing state corruption.

How to identify reentrancy risks when blocking COM calls dispatch timer callbacks mid-execution?

Identify reentrancy risks by pinpointing potential issues where COM's STA message pump can dispatch timer or hotkey callbacks mid-execution during blocking COM calls, even when Critical "On" is active, ensuring application stability and preventing state corruption.