869 件 ・ 関連度順
概要と使いどころ
Compare before/after Coval runs using matched cases, stable metric versions and inspected conversation evidence. Use to assess a regression or proposed improvement; does not automatically launch or tune anything.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnostic method for any bug, failure, regression, flake, or slowdown. Use before proposing a fix: something is broken, throwing, not saving, not showing, or 'worked yesterday'; on 'debug this' or 'find the root cause'; and immediately after a fix attempt did not work.
日本語の概要は準備中です。原文の説明を表示しています。
The bar every automated test or guard must clear: green only when the real system works. Use when writing, fixing, or reviewing a test, mock, stub, fixture, snapshot, or self-test; adding a regression test for a bug; or about to call work done because tests pass.
日本語の概要は準備中です。原文の説明を表示しています。
AI支援開発のためのリグレッションテスト戦略。データベース依存なしのサンドボックスモードAPIテスト、自動バグチェックワークフロー、同一モデルがコードの作成とレビューを行う際のAIの盲点を検出するパターン。
Use when adding or repairing Spark regression tests for asynchronous ownership, cancellation, persistence, restart recovery, or cross-surface projections. Not a coverage campaign, performance benchmark, source-text policy check, or full delivery review.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically finds and fixes bugs using proven debugging techniques. Traces from symptoms to root cause, implements fixes, and prevents regression.
日本語の概要は準備中です。原文の説明を表示しています。
Describes the NemoClaw plugin and blueprint architecture and how they orchestrate the OpenClaw sandbox. Use when looking up architecture, plugin structure, or blueprint design. Trigger keywords - nemoclaw architecture, nemoclaw plugin blueprint structure, nemoclaw cli commands, nemoclaw command reference, nemoclaw network policy, sandbox egress control operator approval, nemoclaw troubleshooting, nemoclaw debug sandbox issues.
日本語の概要は準備中です。原文の説明を表示しています。
Statistical analysis toolkit. Hypothesis tests (t-test, ANOVA, chi-square), regression, correlation, Bayesian stats, power analysis, assumption checks, APA reporting, for academic research.
日本語の概要は準備中です。原文の説明を表示しています。
Apply systematic performance optimization techniques when writing or reviewing code. Use when optimizing hot paths, reducing latency, improving throughput, fixing performance regressions, or when the user mentions performance, optimization, speed, latency, throughput, profiling, or benchmarking.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic performance profiling and optimization methodology. Covers CPU profiling, memory profiling, heap analysis, goroutine/thread analysis, FlameGraph generation, latency profiling, database query profiling, network I/O profiling, and continuous performance regression detection. USE WHEN: investigating performance issues, optimizing slow code, reducing memory usage, diagnosing GC/CPU bottlenecks, finding N+1 queries, analyzing pprof/flamegraph output, or establishing a performance baseline. Triggers on "profiling", "performance analysis", "slow code", "flame graph", "pprof", "heap dump", "memory leak", "CPU spike", "bottleneck".
日本語の概要は準備中です。原文の説明を表示しています。
Systematic debugging methodology covering root cause analysis, log-based debugging, production debugging, memory leak diagnosis, deadlock detection, performance anomaly investigation, and reproducible bug reproduction. Distilled from real experience at Google, DeepMind, ByteDance, and Huawei. USE WHEN: investigating production incidents, debugging hard-to-reproduce bugs, analyzing crash dumps, finding race conditions, diagnosing memory leaks, debugging performance regressions, or any situation requiring systematic root cause analysis. Triggers on "debugging", "root cause", "bug", "crash", "segfault", "deadlock", "race condition", "memory leak".
日本語の概要は準備中です。原文の説明を表示しています。
Eight drift classes scanned continuously. Catches regressions before they ship.
日本語の概要は準備中です。原文の説明を表示しています。
Test and assure quality — test plan, QA, coverage, unit test, integration test, end-to-end, performance, benchmark, regression. Applies TDD and FIRST principles for the CTO office's tester.
日本語の概要は準備中です。原文の説明を表示しています。
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
日本語の概要は準備中です。原文の説明を表示しています。
Build or improve UI test coverage for visual regression, interactions, and accessibility. Use when the user asks for a test strategy, automated tests, testing setup, or fixes to flaky UI tests. A one-time browser inspection or visual review does not require a new test suite.
日本語の概要は準備中です。原文の説明を表示しています。
Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Gates CI on perf regressions. Automated threshold alerts, baseline tracking, trend reports.
日本語の概要は準備中です。原文の説明を表示しています。
Perform repository-aware code reviews focused on bugs, regressions, architectural violations, missing tests, and operational risks. Use when the user asks for review of diffs, pull requests, patches, or implementation quality.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes UEFI bootkit persistence mechanisms including firmware implants in SPI flash, EFI System Partition (ESP) modifications, Secure Boot bypass techniques, and UEFI variable manipulation. Covers detection of known bootkit families (BlackLotus, LoJax, MosaicRegressor, MoonBounce, CosmicStrand), ESP partition forensic inspection, chipsec-based firmware integrity verification, and Secure Boot configuration auditing. Activates for requests involving UEFI malware analysis, firmware persistence investigation, boot chain integrity verification, or Secure Boot bypass detection.
日本語の概要は準備中です。原文の説明を表示しています。
Browser automation and testing using Playwright MCP server for visual regression, accessibility, route testing, and screenshot capture.
日本語の概要は準備中です。原文の説明を表示しています。
Generate or materially revise a repository-local test plan, QA plan, acceptance matrix, or regression checklist on explicit request or when one concrete testability gap blocks formal DEFINE; do not trigger for ordinary implementation, test execution, TDD, review, or completion claims.
日本語の概要は準備中です。原文の説明を表示しています。
Sets up Storybook for component documentation with controls, actions, accessibility testing, and visual regression. Use when users request "Storybook setup", "component documentation", "UI library", "component stories", or "design system docs".
日本語の概要は準備中です。原文の説明を表示しています。
Creates comprehensive permission tests ensuring RBAC doesn't regress with test matrices, CI gating, and authorization coverage. Use for "RBAC testing", "permission tests", "authorization testing", or "access control tests".
日本語の概要は準備中です。原文の説明を表示しています。
Builds end-to-end browser tests for critical user flows using Playwright or Cypress. Includes selector strategies, test data management, page objects, and visual regression testing. Use for "E2E testing", "browser tests", "Playwright", or "Cypress tests".
日本語の概要は準備中です。原文の説明を表示しています。