Repair Semaphore Permit Leaks

The problem

Concurrency gates often fail silently when semaphores leak permits after exceptions or cancellations. This leads to services that gradually stop accepting work despite having idle resources or, conversely, exceeding configured limits.

What it does

• Identifies every semaphore instance and guarded resource across the codebase.
• Reconstructs permit ownership timelines for success, timeout, and cancellation paths.
• Repairs acquisition/release symmetry to ensure every permit has exactly one terminal disposition.
• Fixes partial-failure cleanup in weighted/multi-permit acquisition logic.
• Implements idempotent, owner-aware release mechanisms without altering business retry logic.

Why this beats prompting it yourself

General LLMs often suggest simple try-finally blocks that fail during complex race conditions or async cancellations. This skill uses a strict conservation invariant and permit-ownership registry to ensure logic is mathematically sound across all possible failure states.

Use cases

• Fixing services that eventually hang or "freeze" under high load.
• Ensuring worker pools don't exceed memory limits due to double-releases.
• Hardening async task submissions where permits are stranded on submission failure.
• Converting sleep-based race tests into deterministic concurrency barriers.

Known limitations

Does not modify global infrastructure settings like external load balancer capacity. Requires repository access to inspect local synchronization primitives.