'concurrency' 검색 결과

Write and refactor C++20/23 applications, addressing memory management, concurrency, and performance bottlenecks. Produce interfaces, implementations, tests, and relevant CMake updates, then check runtime errors and measure performance before applying targeted optimizations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Refactoring existing code with C++20/23 features
• Investigating memory errors and undefined behavior
• Improving performance through profiling and benchmarks

Reviews Rust applications and libraries for security issues involving unsafe code, memory safety, concurrency, calls across language boundaries, panics, and async runtimes. Coordinates specialized reviewers and produces Markdown and SARIF reports, a format for analysis tools.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Auditing unsafe Rust code
• Reviewing calls across language boundaries
• Checking concurrency and async runtime hazards

Run stepped HTTP load tests with ab/wrk, ramping concurrency levels to collect p50/p90/p99 latency, detect performance inflection points, and recommend optimal concurrency. Triggered by requests like 'load test this URL', 'benchmark my API', 'find the max concurrency', or mentions of p99 latency, throughput saturation, or capacity planning.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Golang concurrency design — goroutine lifecycle and leak prevention, channels and `select`, channel ownership and direction, `sync.Mutex`/`RWMutex`/`sync.Map`/`sync.Once`/atomics, `errgroup`, `singleflight`, worker pools, and fan-out/fan-in pipelines. Use when writing or reviewing concurrent Go code, when choosing between channels and mutexes, when protecting a shared map or counter, or when a goroutine has no clear exit. Not for defensive coding unrelated to concurrency such as nil panics, slice aliasing, or numeric overflow (→ See `samber/cc-skills-golang@golang-safety` skill), and not for debugging a specific hung, crashing, or racing program after the fact (→ See `samber/cc-skills-golang@golang-troubleshooting` skill).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when writing ANY async code, actors, or threads in an Apple-platform app, or seeing ANY concurrency error. Covers Swift 6 concurrency, @MainActor, Sendable, data races, async/await patterns.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Report concurrency and parallelism for a session — how many agents ran in parallel, concurrency-lane utilization, peak parallel width, and serialization bottlenecks (sequential chains that could have run as parallel lanes) — using the Agent Monitor workflow intelligence API. Use when checking whether a multi-agent session used parallelism efficiently.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review Java concurrency code for thread safety, race conditions, deadlocks, and modern patterns (Virtual Threads, CompletableFuture, @Async). Use when user asks "check thread safety", "concurrency review", "async code review", or when reviewing multi-threaded code.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Go is the language of infrastructure. From Docker to Kubernetes to the entire cloud-native ecosystem, Go powers the systems that run the internet. It's not about what you can build - it's about what you won't break at 3 AM. This skill covers idiomatic Go patterns, error handling, concurrency with goroutines and channels, HTTP servers, microservice architecture, and the standard library that makes Go so powerful. Key insight: Go's simplicity is a feature. Fight the urge to abstract. Embrace boring, readable code. 2025 lesson: The teams succeeding with Go are the ones who resist overengineering. A main.go with 500 lines beats a "clean architecture" with 50 packages. Use when "golang, go service, go microservice, goroutine, channels, go http, go api, go backend, gin, fiber, chi router, go concurrency, go, golang, microservices, backend, concurrency, goroutines, channels, http, api" mentioned.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Raise real concurrency in asyncio LLM batch scorers built on the OpenAI SDK (AsyncOpenAI, including OpenAI-compatible providers like DeepSeek). Use when: (1) raising an asyncio.Semaphore above ~100 produces no throughput gain, (2) a batch pipeline saturates near 100 in-flight requests despite a larger semaphore, (3) planning a high-concurrency campaign against a provider with no hard rate limit (DeepSeek v4-flash tolerates 2000+ in flight). Root cause: AsyncOpenAI's default httpx pool caps max_connections at 100, silently bottlenecking any larger semaphore — you must pass a custom http_client with httpx.Limits sized to the semaphore.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Senior Kotlin specialist code review — framework-agnostic. Use whenever the user asks to review, audit, critique, or get feedback on Kotlin code, a file, a class, a function, a module, a diff, a branch, a commit, or a pull request. Judges Kotlin language idioms, logic correctness, architecture and layering, concurrency (coroutines, Flow, structured concurrency, cancellation, race conditions), null safety, exception safety, testability, performance, and security. Detects force-unwraps, unchecked casts, GlobalScope, leaked mutability, broken structured concurrency, hidden side effects, weak abstractions, untestable seams, allocation hot spots, weak crypto, input-validation gaps, and PII logging. Outputs prioritized findings with file:line anchors and minimal-diff fixes. No assumptions about DI framework, UI framework, or build system.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Concurrency v3 — threads, async/await, mutex, channels, actor model, CSP, lock-free, distributed

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reviews Swift code for concurrency correctness, modern API usage, and common async/await pitfalls. Use when reading, writing, or reviewing Swift concurrency code.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Swift 6.2 Approachable Concurrency — デフォルトでシングルスレッド、明示的なバックグラウンドオフロードに@concurrent、メインアクター型の分離適合。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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 and structured concurrency, scoped values, backpressure, cancellation discipline, and observability for concurrent systems. Part of the skills-for-java project

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Kotlin Coroutines와 Flow로 Android 및 Kotlin Multiplatform의 비동기 작업과 데이터 갱신을 구현하고 병렬 실행, 화면 상태, 취소, 오류 처리와 테스트를 다룹니다.

• 여러 데이터를 병렬로 불러옵니다
• StateFlow로 화면 상태를 관리합니다
• 검색 입력을 조절하고 통신을 재시도합니다

Build concurrent Go applications with goroutines, lightweight execution units, and channels for communication. Apply patterns for worker pools, cancellation, synchronization, and orderly shutdown, and investigate race conditions when concurrent operations access shared data.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implement a worker pool for concurrent jobs
• Connect processing stages with channels
• Manage cancellation and orderly shutdown

Guides background processing in Node.js and TypeScript with BullMQ and Redis. Covers job queues, which hold tasks for later execution, along with scheduling, priorities, rate limits, worker concurrency, and dependencies between processing steps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Design a queue for background tasks
• Schedule jobs for later or repeated execution
• Organize dependent steps into a job flow

Review agent-written code changes before merge, focusing on concrete correctness defects. Uses independent subagent reviews, targeted verification, and fresh checks after substantial repairs, with a deeper evidence-based process for security, concurrency, persistence, or data-loss risks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing agent-written changes before merge
• Rechecking a substantial bug fix
• Examining security, concurrency, or data-loss risks

Write and improve Go code with clear error handling, interface design, and tests. Build concurrent workflows, where tasks run independently, with controlled worker counts, cancellation, and explicit shutdown paths for background work.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building worker pools with concurrency limits
• Adding cancellation and deadlines to long-running work
• Reviewing interfaces and package design

Review Doris code changes using project-specific checklists for data correctness, concurrency, memory safety, compatibility, performance, and tests. Trace related code paths and explain findings with concrete failure scenarios, using query plan trees when reviewing optimizer behavior.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review newly completed Doris code changes
• Check concurrency and memory management in related code paths
• Assess compatibility and test coverage before merging

Explain code structure and behavior with text diagrams, including before-and-after views of changes. Trace data flow and state changes, clarify design choices, and examine assumptions, possible failures, and interactions between tasks running at the same time.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Understanding a patch through before-and-after diagrams
• Tracing a class's behavior and state changes
• Mapping component relationships across a codebase

Review Apache Pinot concurrency and state safety when locks, shared callbacks, lifecycle, or distributed metadata change.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Troubleshoot Golang programs systematically - find and fix the root cause. Use when encountering bugs, crashes, deadlocks, races, or unexpected behavior in Go code. Covers debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve, race detection, GODEBUG tracing, and production debugging. Start here for any 'something is wrong' situation. Not for interpreting profiles or benchmarking (→ See `samber/cc-skills-golang@golang-benchmark` skill), applying optimization patterns (→ See `samber/cc-skills-golang@golang-performance` skill), or designing new code (→ See `samber/cc-skills-golang@golang-safety` skill for defensive coding, `samber/cc-skills-golang@golang-concurrency` skill for concurrency design).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze and control AssemblyAI account request limits, concurrency, backoff, and admission queues. Use when handling 429s or planning throughput. Trigger with "AssemblyAI rate limit", "AssemblyAI concurrency", or "AssemblyAI backoff".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.