Audit Lifecycle
Testing & Qualityaudit-lifecycleAudit Lifecycle is an Agent Skill for testing & quality published in the ben-manes/caffeine repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Analyze shutdown, close, and GC-of-cache lifecycle correctness
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/ben-manes/caffeine/blob/HEAD/.claude/skills/audit-lifecycle/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/audit-lifecycle, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Analyze the cache for defects during shutdown, close, and garbage collection of the cache instance itself.
Assume at least one shutdown or lifecycle race exists. If your analysis yields zero findings, re-examine scheduler/executor lifecycle and in-flight operations during close — explain specifically why no race is possible.
-
Operations racing with close/cleanup: get/put/compute during cleanUp() or GC? close() state transition? Operations after close()?
-
Scheduler lifecycle: Does the scheduled future prevent cache GC? Can scheduler fire after cache is collected? Is the task cancelled on close?
-
Executor lifecycle: Reference cycle between cache and executor? RejectedExecutionException handling when executor is shut down?
-
Removal listener drain on shutdown: Are pending notifications delivered or dropped? Notifications lost if executor shuts down first?
-
In-flight operations during shutdown:
- CacheLoader.load() in progress when cache closes
- Refresh future's whenComplete callback after close
- CompletableFuture value pending when cache closes
-
Multiple close calls: Is close() idempotent? Concurrent close() corruption?
-
Finalizer / Cleaner interactions: Reference queues outliving the cache? Reference queue processing accessing dead cache?
-
jcache manager/cache close: Is teardown symmetric with setup — the OSGi context-classloader swap applied on destroy/close as on create/get; in-flight futures awaited; user Closeables (writer, loader, listeners, expiry) closed exactly once under the right classloader?
For each defect: state the lifecycle transition, provide a concrete scenario, state the observable incorrect behavior.