테스트·보안 스킬

Native Rust browser automation CLI for AI agents. Use when the user needs to interact with websites, navigate pages, fill forms, click buttons, take screenshots, share a live browser view, narrate browser actions, extract structured data, run assertions, test web apps, mock network requests, or automate any browser task. Triggers include "open a website", "fill out a form", "take a screenshot", "show me the browser", "share the screen", "pause the browser", "step through this", "scrape data", "test this web app", "login to a site", "visual regression test", or any task requiring programmatic web interaction.

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

Native Rust browser automation CLI for AI agents. Use when the user needs to interact with websites — navigating pages, filling forms, clicking buttons, taking screenshots, sharing a live browser view, narrating browser actions, extracting structured data, running assertions, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "show me the browser", "share the screen", "pause the browser", "step through this", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", "visual regression test", "check for prompt injection", or any task requiring programmatic web interaction.

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

Design, configure, test, bake, and validate Blender physical effects including Cloth, Soft Body, Rigid Body, collisions, constraints, Fluid, smoke, fire, Dynamic Paint, Ocean, Wave, particles, Boids, force fields, fracture, debris, and secondary effects. Use when gravity, inertia, collision, flexibility, pressure, flow, flocking, emission, or breaking causes the requested result.

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

Build and validate Blender 5.2 Cycles 3D-to-2D materials using four camera-plane-offset Shader Raycast tests to derive an editable silhouette mask, combined with Cycles-compatible toon or flat shading. Use when a Cycles render needs an in-material outline without Shader to RGB.

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

Audit Blender scenes and assets for topology, transforms, normals, surface continuity, classified connections, intersections, modifier/node intent, procedural performance, simulation stability, protected-scene changes, and fixed-view visual evidence. Use after every major modeling or simulation stage and before render, bake, export, or claims of completion.

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

Build, inspect, audit, and refactor Blender Geometry Nodes systems for procedural models, instancing, modular effects, curves, scattering, flocks, data visualization, fields, simulation zones, and node-graph cleanup. Use whenever a Blender task specifically calls for Geometry Nodes, reusable procedural node graphs, node connections/layout, or a scalable procedural asset.

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

Before removing code that looks redundant, wasteful, or "wrong" based on log observations or code review instinct, grep the test suite for tests whose names describe the exact behavior you're about to remove. A test whose title literally describes the "weird" thing (e.g. "calls play() even when player reports playing", "retries even when first call succeeded", "skips cache even when fresh") is a load-bearing workaround, and the production log you're reacting to is probably the workaround working as designed — not a bug. Use when: (1) Tempted to remove a function call that "looks redundant" based on a production log, (2) About to "simplify" a conditional that seems to always take the same branch, (3) Reviewing code and thinking "why would anyone write this?", (4) A log line shows a state that seems impossible or contradictory (e.g. playing=true but positionMs=0 for seconds), (5) CI surfaces a failing test whose name describes exactly what your fix removed.

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

Fix "ref.listen can only be used within the build method of a ConsumerWidget" assertion error in Flutter Riverpod 3.x. Use when: (1) ConsumerStatefulWidget crashes with "Failed assertion: line 492 pos 7: 'debugDoingBuild'" in flutter_riverpod consumer.dart, (2) ref.listen is called inside initState, addPostFrameCallback, or any lifecycle method other than build(), (3) All widget tests fail with this assertion from scheduler callback. Applies to flutter_riverpod 3.0+ with ConsumerStatefulWidget.

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

Fix misleading Flutter/Dart test failures where expected data is empty ([]) or default values instead of the mocked response, caused by stale Mockito generated mocks or missing stubs being silently swallowed by try/catch in provider/repository code. Use when: (1) Test expects non-empty data but gets [], (2) Mock stubs for a method are set up but the code under test returns fallback/empty results, (3) A PR added new methods to a service class and tests that previously passed now fail with misleading "expected X, actual: empty" assertions, (4) "Generated files are out of date" CI error alongside test failures. The root cause is MissingStubError thrown by unstubbed mock methods, caught by production try/catch blocks, causing silent fallback to empty state.

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

Fix Gorse recommendation engine pods crashing with "user: unknown userid 65532" error. Use when: (1) Gorse master/server/worker pods show CrashLoopBackOff or Error status, (2) Logs show "failed to get user directory" with unknown userid, (3) Running gorse containers with runAsNonRoot security context and custom UID. The gorse images call os.UserHomeDir() at startup which requires the UID to exist in /etc/passwd.

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

Fix black camera/microphone preview in Flutter macOS apps launched via `flutter run` from a terminal emulator (cmux, iTerm, Terminal.app, VS Code integrated terminal, Cursor, etc.). Use when: (1) camera plugin reports initialized but preview is black with no frames, (2) logs show "initialization completed via timeout" or similar first-frame timeout fallback, (3) AVCaptureSession.startRunning() returns without error but zero frames arrive, (4) the app's Info.plist has NSCameraUsageDescription and entitlements (com.apple.security.device.camera, audio-input) are correctly set, (5) no permission dialog ever appears, (6) same failure mode for microphone. Root cause is macOS TCC attributing camera/mic requests to the *responsible process* (the parent terminal) rather than the Flutter app itself. TCC refuses to prompt because the terminal is hardened-runtime without a camera entitlement, and silently denies. Not a bug in the camera plugin — would reproduce with ANY camera code.

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

Investigate a GitHub issue and produce a structured implementation plan. Fetches issue details, explores the codebase, identifies affected layers (UI, BLoC, Repository, Client), and outputs a step-by-step plan with files to modify, testing strategy, and risk assessment. Works for bugs, features, and tasks. Invoke with /plan.

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

Fix test failures when adding retry/fallback logic causes mock call count mismatches. Use when: (1) Test fails with "Expected: <1>, Actual: <2>" or similar call count errors after adding retry or fallback mechanisms, (2) MissingStubError appears for methods in new fallback code paths, (3) Mockito verify().called(N) assertions fail after behavior changes. Applies to Dart/Flutter with Mockito, but pattern is universal.

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

Fix flaky Flutter/Dart tests that fail in CI but pass locally due to unhandled Future rejections. Use when: (1) Test passes locally but fails in CI with cryptic errors, (2) Test creates Futures that will throw errors (e.g., network calls to fake URLs), (3) Even with .catchError() at the end, test still fails, (4) Error message shows test name but truncated error like "ROR]" or "[ERROR]". Solution: Avoid creating Futures that will reject; test state machine behavior with synchronous operations instead.

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

Fix LRU-bounded Flutter/bloc state classes that silently lose insertion-order updates. Use when: (1) a state class uses `Equatable` with a `LinkedHashMap<K, V>` field to preserve insertion order (LRU, MRU, recent-items caches), (2) `Cubit.emit` appears to drop emissions when an existing key is re-inserted or moved to most-recent, (3) LRU eviction evicts the "wrong" entry after a refresh, (4) a test that reports the same key twice and then overflows the cap sees the refreshed entry evicted instead of the oldest. Root cause: Equatable's default map comparison is structural (unordered), so reordering without changing keys/values produces an "equal" state that `Cubit.emit` suppresses.

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

Run and debug Flutter E2E integration tests that exercise the real app against a local Docker backend (no mocks). Use when running E2E tests, debugging failures, or working on the local harness.

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

Fix Dart/Flutter services where calling start() after stop() is a silent no-op because stop() sets a _disposed (or similar) flag that start()'s guard short-circuits on. Use when: (1) A repository/service/controller has startListening/stopListening, subscribe/unsubscribe, open/close, or similar lifecycle methods, (2) Re-opening the service after closing it appears to do nothing — no subscription, no events, no error, (3) Unit tests that only exercise a single mount/open/start cycle pass while the real app breaks on the second visit to a screen, (4) A boolean flag is used both for "in the middle of tearing down this instance forever" AND for "currently stopped, can be re-started". Common in Riverpod/Bloc-driven screens that wire startListening() in initState and stopListening() in dispose — the second time the user visits the screen, nothing happens.

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

Fix Fastly Compute Rust crate `cargo test` failures with "ld: symbol(s) not found" errors for Fastly SDK symbols like `_version_set`, `_body_new`, `_req_send` on native host builds. Use when: (1) `cargo test` on a Fastly Compute crate fails at link time with errors mentioning libfastly and symbols with names like `fastly::http::response::handle::...`, (2) You added a `#[cfg(test)]` module to a file in a Fastly Compute binary crate and the tests never seem to run or fail to link, (3) Existing `#[cfg(test)]` modules in src/main.rs or its sibling modules appear dead despite being present in the source tree, (4) `cargo test --lib` works but `cargo test` fails.

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

Fix Flutter test failure "A Timer is still pending even after the widget tree was disposed". Use when: (1) Widget tests fail with timer pending error, (2) dispose() contains Future(), Future.delayed(), or Timer calls, (3) Riverpod provider modifications in dispose(). The fix is to use deactivate() instead of dispose() for cleanup that might trigger async work.

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

Create the required PR-ready summary block, branch suggestion, title, and draft description for openai-guardrails-python after runtime, tests, examples, build/test configuration, or behavior-impacting docs change.

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

Perform the repository's risk-tiered independent final review before implementation completion. Use only when explicitly invoked or when repository instructions require it after behavior-impacting implementation work; audit the complete task diff, supported contracts, lifecycle and security boundaries, complexity, and tests before final verification.

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

Review an openai-guardrails-python release plan or final release candidate against the previous remote tag, determine the compatible release type, audit runtime and packaging risk, inspect current CI, and produce an English ship-or-block report. Use for pre-release readiness checks, not ordinary PR review or implementation.

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

Design game performance testing strategy. Use when the user says "performance test" or "benchmark"

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

Review test quality and coverage. Use when the user says "test review" or "review tests"

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