Run any Skill in Manus with one click

Get Started

$pwd:

audit-feature-interaction

Name: Audit Feature Interaction
Author: ben-manes

// Analyze feature interaction pairs and triples for concurrent defects

Run Skill in Manus

$ git log --oneline --stat

stars:17,676

forks:1,688

updated:April 13, 2026 at 09:17

SKILL.md

readonly

name	audit-feature-interaction
description	Analyze feature interaction pairs and triples for concurrent defects
context	fork
agent	auditor
disable-model-invocation	true

Analyze the cache for defects arising from multiple features operating simultaneously on the same entry.

Assume at least one feature interaction bug exists. If your analysis yields zero findings, re-examine the top-priority pairs below — explain specifically why no interleaving produces a bug.

Priority ranking (from confirmed historical bugs):

Refresh + expiration (D+B) — most-bugged interaction historically
Reference collection + any feature (C+*) — value reference visibility
Async completion + any feature (F+*) — future lifecycle edge cases
Eviction + weight change (A+H) — counter drift during transitions

Features: A. Eviction (size/weight limit exceeded) B. Expiration (afterAccess, afterWrite, variable) C. Reference collection (weak key, weak value, soft value GC) D. Refresh (automatic reload) E. Loading (CacheLoader / computeIfAbsent) F. Async completion (CompletableFuture values) G. Listener notification (removal listener, eviction listener) H. Weight change (Weigher returning different weight for new value)

For each pair (A,B), (A,C), ..., (G,H) — 28 pairs total:

Can both features trigger simultaneously on the same entry?
If yes, construct the most adversarial interleaving.
Trace step-by-step: correct processing? notifications? final state? cleanup?

After all pairs, identify highest-risk TRIPLE interactions:

Eviction + expiration + listener exception
Refresh + async completion + GC collection
Weight change + eviction + compute

High-risk pairwise combinations:

Eviction during refresh (entry evicted while refreshing)
Expiration during compute (entry expires mid-computation)
GC during async completion (future completes after weak ref collected)
Weight change during eviction
Listener exception during any other feature

For each defect: state the features involved, provide the interleaving, state the incorrect behavior.

related-skills.json

same repository

audit-sibling-divergence.md

from "ben-manes/caffeine"

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) and requires a concrete witness scenario where the two paths diverge observably.

2026-05-1717.7k

audit-temporal-walk.md

from "ben-manes/caffeine"

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 (~8-14 hours) and rare-run (every several months or before a major release).

2026-05-0917.7k

audit-contract-drift.md

from "ben-manes/caffeine"

Find places where documented API contracts and the implementation diverge

2026-04-2717.7k

audit-exception-safety.md

from "ben-manes/caffeine"

Audit exception safety and failure atomicity across all throw sites

2026-04-1317.7k

audit-iteration.md

from "ben-manes/caffeine"

Analyze concurrent iteration and view consistency guarantees

2026-04-1317.7k

audit-jmm.md

from "ben-manes/caffeine"

Java Memory Model audit of all VarHandle/volatile field access modes

2026-04-1317.7k

package.json

"author": "ben-manes"

"repository": "ben-manes/caffeine"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

Software Quality Assurance Analysts and TestersL4

name	audit-feature-interaction
description	Analyze feature interaction pairs and triples for concurrent defects
context	fork
agent	auditor
disable-model-invocation	true

Analyze the cache for defects arising from multiple features operating simultaneously on the same entry.

Assume at least one feature interaction bug exists. If your analysis yields zero findings, re-examine the top-priority pairs below — explain specifically why no interleaving produces a bug.

Priority ranking (from confirmed historical bugs):

Refresh + expiration (D+B) — most-bugged interaction historically
Reference collection + any feature (C+*) — value reference visibility
Async completion + any feature (F+*) — future lifecycle edge cases
Eviction + weight change (A+H) — counter drift during transitions

For each pair (A,B), (A,C), ..., (G,H) — 28 pairs total:

Can both features trigger simultaneously on the same entry?
If yes, construct the most adversarial interleaving.
Trace step-by-step: correct processing? notifications? final state? cleanup?

After all pairs, identify highest-risk TRIPLE interactions:

Eviction + expiration + listener exception
Refresh + async completion + GC collection
Weight change + eviction + compute

High-risk pairwise combinations:

Eviction during refresh (entry evicted while refreshing)
Expiration during compute (entry expires mid-computation)
GC during async completion (future completes after weak ref collected)
Weight change during eviction
Listener exception during any other feature

For each defect: state the features involved, provide the interleaving, state the incorrect behavior.

audit-feature-interaction

More from this repository

More from this repository