「tests」の検索結果

Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.

日本語の概要は準備中です。原文の説明を表示しています。

Add a new E2E test case to tests/e2e/prompts.yaml for LangSmith evaluation. Use when adding interaction pairs to test, covering new ANSM drug classes, or rebalancing eval coverage.

日本語の概要は準備中です。原文の説明を表示しています。

Review code changes for correctness defects, regressions, security risks, data-integrity problems, concurrency hazards, and missing meaningful tests. Use for pull requests, branches, commits, patches, or working-tree reviews; do not use for implementation unless the user separately requests fixes.

日本語の概要は準備中です。原文の説明を表示しています。

Verify like Fable 5 — obsessive, systematic, evidence-based quality assurance woven into your reasoning. Use this skill when you have just written or modified code, need to confirm something works, are running tests, or need to validate output against requirements.

日本語の概要は準備中です。原文の説明を表示しています。

Debug like Fable 5 — systematic root cause analysis with natural reasoning flow. Use this skill when you encounter an error, unexpected behavior, failing tests, or anything that does not work as intended.

日本語の概要は準備中です。原文の説明を表示しています。

Prices research, tests, surveys, dashboards and experiments before running them, by computing how much the result would raise expected utility - which is zero whenever no outcome would change the decision. Use when someone proposes an A/B test, user survey, market study, competitor analysis, analytics build, consultant, pilot, or "let's gather more data", and when deciding how large a study needs to be.

日本語の概要は準備中です。原文の説明を表示しています。

Implement a ready rolling-wave slice without locking it down with broad tests yet. Use when the user explicitly wants to code the current docs/rolling-wave/{project}/slices/NNN-slug.md slice, mark it in progress while working, implement small or cohesive work in the main context by default, use one to three gpt-5.6-terra workers only for genuine parallel chunks or large discovery/mechanical work where delegation pays for its handoff cost, pause or hand off chunks marked human-fit when appropriate, record implementation notes and final-test backlog, preserve the original slice contract, and mark completed implementation ready for review.

日本語の概要は準備中です。原文の説明を表示しています。

Review local git changes before opening a PR or merging. First review all local tracked and untracked files; if none exist, review the current branch against a requested base branch or the Git Town parent branch. Use zero to three review subagents only when risk, diff size, language specificity, or uncertainty justifies the token cost, then report high-confidence bugs, regressions, risky assumptions, and missing tests. Use when the user asks for code review, local review, branch sanity check, pre-PR review, or review of work-in-progress changes.

日本語の概要は準備中です。原文の説明を表示しています。

Migrate a UI component from one framework to another, preserving behavior and tests.

日本語の概要は準備中です。原文の説明を表示しています。

Check whether changed source files have corresponding test files. Use for code quality review before merging a PR, or when asked whether new code has tests.

日本語の概要は準備中です。原文の説明を表示しています。

TDD Refactor Phase - Improve code while keeping tests green using Simple Design Rules and APP mass

日本語の概要は準備中です。原文の説明を表示しています。

Generates complete features from natural language — components, API routes, migrations, types, and tests.

日本語の概要は準備中です。原文の説明を表示しています。

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

日本語の概要は準備中です。原文の説明を表示しています。

Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.

日本語の概要は準備中です。原文の説明を表示しています。

Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO NOT TRIGGER when: the idea is already turned into a spec or PRD; bug fixes or refactors; the idea is hardened and you are ready to write the PRD → creating-prd.

日本語の概要は準備中です。原文の説明を表示しています。

Test coverage quality analysis — behavioral coverage, critical gap identification, test resilience evaluation.

日本語の概要は準備中です。原文の説明を表示しています。

Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.

日本語の概要は準備中です。原文の説明を表示しています。

Test coverage quality analysis — behavioral coverage, critical gap identification, test resilience evaluation.

日本語の概要は準備中です。原文の説明を表示しています。

Bun runtime, package manager, bundler, and test runner. Use when running scripts with bun, managing packages, serving HTTP with Bun.serve, querying databases with Bun.sql/bun:sqlite/Bun.redis, shell scripting with $, using S3/file I/O, writing tests with bun:test, bundling or compiling to executable, or using any Bun-specific API (spawn, glob, semver, FFI, workers, plugins, HTMLRewriter).

日本語の概要は準備中です。原文の説明を表示しています。

Systematically find and fix performance problems in applications, frontend and backend, by measuring first. Use this skill whenever the user reports slow endpoints, high latency, poor throughput, memory leaks, large bundles, or slow page loads; wants to profile with cProfile, py-spy, Chrome DevTools, Node --cpu-prof, or perf; run load tests with locust or k6; set performance budgets or SLOs; optimize database queries (EXPLAIN, indexes, N+1); add caching (Redis); improve frontend performance (code splitting, lazy loading, image optimization, memoization, virtualization); or tune the network (CDNs, gzip/br, HTTP/2/3). Also trigger for p50/p95/p99 latency, throughput, error rate, connection pooling, async vs threads, GIL, and memory leak investigations.

日本語の概要は準備中です。原文の説明を表示しています。

Build, modify, run, test, screenshot, record, and export Godot 4.x games with the gdx CLI. Use when Codex needs to create a new Godot game project, attach to an existing Godot project, generate GDScript, build scenes/resources from JSON specs, edit a running scene through the gdx daemon, capture screenshots, record animation clips, send input, inspect game state, run Godot tests, or produce exports through gdx.

日本語の概要は準備中です。原文の説明を表示しています。

Use when verifying a story or ticket implementation against its spec and acceptance criteria - per-AC verdicts with file:line evidence and proving tests, code reuse and design conformance, dead code, stale docs, comment discipline. Finds the spec from an explicit path, the ticket key in the branch name, or plan files - and asks rather than guessing. For defect-hunting code review use dotnet-techne-code-review instead. Keywords: story QA, acceptance criteria, spec conformance, AC coverage, definition of done, dead code check, reuse check, comment check, verify story, QA this branch.

日本語の概要は準備中です。原文の説明を表示しています。

Measure, root-cause, fix, verify and record performance contention on a developer machine: cloud-sync daemons (iCloud Drive, OneDrive, Dropbox, Google Drive), file indexers, AI-tool MCP server fleets, and automation browsers left behind by tests and browser skills. Trigger when the machine is slow, apps freeze, browser or MCP tool calls time out, load exceeds the core count, or before and after any UI/UX/performance test run. Includes the L0–L4 optimisation scale and the test-hygiene contract.

日本語の概要は準備中です。原文の説明を表示しています。

Use BEFORE writing any test — enumerate cases per behavior (happy / boundary / error / abuse), prioritize by likelihood × impact, cross-check via subagent — even if the user just says 'add tests'.

日本語の概要は準備中です。原文の説明を表示しています。