بنقرة واحدة
audit-coverage-gaps
Discover test coverage gaps that could hide correctness defects
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Discover test coverage gaps that could hide correctness defects
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Audit the adaptive window hill-climber and region-resize logic for implementation defects (not algorithm quality)
JSR-107 (JCache) spec-conformance audit
Audit explicit state machines (drain status, node lifecycle, async-value lifecycle) for illegal or missed transitions
Heavyweight history-mining bug audit. Walks the caffeine module's git history chronologically (oldest to HEAD), maintains a forward-tracked issue database, and surfaces concerns introduced by past commits that were never resolved. Catches bugs that snapshot mining cannot — half-fixes invisible from current state, latent+trigger pairs across multi-commit interactions, and partial refactors. Slow (model/effort-dependent; ~24h on Opus + max effort) and rare-run (every several months or before a major release).
Differential audit comparing matched code paths that should behave identically. Spawns one auditor per sibling pair (sync/async, bounded/unbounded, view consistency, bulk vs single, generated node variants, read fast vs slow, adapter conformance) and requires a concrete witness scenario where the two paths diverge observably.
Find places where documented API contracts and the implementation diverge
| name | audit-coverage-gaps |
| description | Discover test coverage gaps that could hide correctness defects |
| context | fork |
| agent | auditor |
| disable-model-invocation | true |
Assume the existing tests miss at least one real defect.
For each public method, identify the hardest-to-test edge cases:
For each edge case, trace the code path. Does the code handle it correctly?
Identify combinatorially hard behavioral dimensions:
For each candidate gap, provide a minimal test case with the specific cache configuration and thread interleaving needed to reach the code path.
Priority ordering:
Focus only on behavioral coverage gaps that could hide correctness bugs.