Results for “race-condition”

Use the status-briefing skill to run `pk-reconcile session-start`, then

Use this skill when a crash has been incorrectly classified as DOT-recordable when it shouldn't be. Covers the § 390.5 criteria, common misclassifications, and challenge process.

JS State Pattern

Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.

Facilitate a structured sprint retrospective to surface insights and produce actionable improvements with owners and deadlines.

Pre-commit/ship code review: Codex default; optional Claude, Pi, Droid, Copilot, Cursor, or OpenCode.

Use when context window is filling up, sessions are getting slow, or you need to preserve state across sessions. For context compression, state snapshots, search-first discipline, and cross-session memory management.

Toggle the statusline quota pace indicator (mode/theme)

Temporarily turn off the requirement that pending changes be reviewed before committing in the current herdr workspace.

查看所有运行中实验的状态，可选自动收集已完成实验并推进流水线

Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.

Burn HUD

Runbook skill for failures: cron error, PA failure, cascade, gateway disconnect, semantic DB stale. Walks: detect → classify → diagnose → notify → log. Replaces ad-hoc failure handling. Triggers: "cron failed", "X is broken", "cascade", "incident", "gateway down", "PA failure".

飞书考勤打卡：查询自己的考勤打卡记录

Provides guidance on acceptable blood sampling conditions for primary aldosteronism screening when ideal early‑morning supine fasting conditions cannot be met. Triggers include when a clinician says “The patient wasn’t fasting/supine” or questions whether non‑ideal sampling affects screening validity.

Evidence-driven tracing lane that orchestrates competing tracer hypotheses in Claude built-in team mode

Diagnose and remove FPS caps so the editor and game run uncapped (or at a target FPS). Use when the user says the editor/game is "locked", "capped", or "stuck" at a frame rate (commonly 60 FPS), asks to "unlock"/"uncap"/"raise" FPS, or wants to set a max FPS. Covers t.MaxFPS, VSync, fixed/smoothed frame rate, and background CPU throttling (EngineSettingsService).

Use this skill when the user asks about refrigerated (reefer) trucking — cold chain compliance, FDA temperature recording requirements, Sanitary Transportation Rule (STR / 21 CFR 1.900-1.934), commodity-specific temperature ranges, refrigeration unit operation, temperature recorder calibration, and how a load is challenged if temperature deviates. Cite 21 CFR Part 1 Subpart Q.

Performance-coaching mode for repeated failures, passive behavior, completion-quality issues, or explicit try-harder requests. Uses structured troubleshooting and evidence-first delivery habits.

Procedurally design an AAA-style open-world FPS map blockout (roads, POIs, fields, forests/treelines, railway/bridges) from a landscape, validate it through gated checks, and materialize it into engine geometry. Use when the user asks to block out or lay out an open-world/FPS map, place roads/POIs/forests/railways procedurally, or turn a blockout plan into splines, paint layers, foliage, and actors.

Score raw leads as HOT/WARM/COOL based on config-driven weights from agency.config.json

Most teams run one test — expected peak for ten minutes — and believe they have

Implement modern concurrency with Virtual Threads and Structured Concurrency in Java. Use when implementing Java Virtual Threads (Java 21), Structured Concurrency with StructuredTaskScope, CompletableFuture pipelines, or debugging race conditions.

当需要克服拖延、激发最大行动力以完成一项重大挑战或转型时

Adopt Swift 6.2's Approachable Concurrency model, which runs code single-threaded by default and uses explicit @concurrent for background offloading, isolated conformances, and MainActor default inference to eliminate data-race errors.

Use this skill when managing post-SAP follow-up testing for a driver. Covers the testing cadence, recordkeeping, what happens if a test is missed, and how to transition the schedule to a new employer.

Trace every user-facing button through its full state change sequence to find bugs where functions individually work but cancel each other out, produce wrong final state, or leave the UI inconsistent.