Agent skill
125-java-concurrency
Use when you need to apply Java concurrency best practices — including thread safety fundamentals, ExecutorService thread pool management, concurrent design patterns like Producer-Consumer, asynchronous programming with CompletableFuture, immutability and safe publication, deadlock avoidance, virtual threads, scoped values, backpressure, cancellation discipline, and observability for concurrent systems. Part of the skills-for-java project
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/125-java-concurrency
Metadata
Additional technical details for this skill
- author
- Juan Antonio Breña Moral
- version
- 0.14.0
SKILL.md
Java rules for Concurrency objects
Identify and apply Java concurrency best practices to improve thread safety, scalability, and maintainability by using modern java.util.concurrent utilities and virtual threads.
What is covered in this Skill?
- Thread safety fundamentals:
ConcurrentHashMap,AtomicInteger,ReentrantLock,ReadWriteLock, Java Memory Model ExecutorServicethread pool configuration: sizing, keep-alive, bounded queues, rejection policies, graceful shutdown- Producer-Consumer and Publish-Subscribe patterns with
BlockingQueue CompletableFuturefor non-blocking async composition (thenApply/thenCompose/exceptionally/orTimeout)- Immutability and safe publication (
volatile, static initializers) - Lock contention and false-sharing performance optimization
- Virtual threads (
Executors.newVirtualThreadPerTaskExecutor()) for I/O-bound scalability ScopedValueoverThreadLocalfor immutable cross-task data- Cooperative cancellation and
InterruptedExceptiondiscipline - Backpressure with bounded queues and
CallerRunsPolicy - Deadlock avoidance via global lock ordering and
tryLockwith timeouts - ForkJoin/parallel-stream discipline for CPU-bound work
- Virtual-thread pinning detection (JFR
VirtualThreadPinned) - Thread naming and
UncaughtExceptionHandlerobservability - Fit-for-purpose primitives:
LongAdder,CopyOnWriteArrayList,StampedLock,Semaphore,CountDownLatch,Phaser
Scope: The reference is organized by examples (good/bad code patterns) for each core area. Apply recommendations based on applicable examples.
Constraints
Before applying any concurrency changes, ensure the project compiles. If compilation fails, stop immediately — compilation failure is a blocking condition. After applying improvements, run full verification.
- MANDATORY: Run
./mvnw compileormvn compilebefore applying any change - SAFETY: If compilation fails, stop immediately — compilation failure is a blocking condition that prevents any further processing
- VERIFY: Run
./mvnw clean verifyormvn clean verifyafter applying improvements - BEFORE APPLYING: Read the reference for detailed good/bad examples, constraints, and safeguards for each concurrency pattern
When to use this skill
- Review Java code for concurrency
Reference
For detailed guidance, examples, and constraints, see references/125-java-concurrency.md.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?