「tests」の検索結果

Review test quality using best practices validation. Use when user says "lets review tests" or "I want to evaluate test quality"

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

S5 of see-it-ship-it: prove it works before saying so. Silent quality checks after every feature, a full review of every file before save and deploy, and the acceptance table (check / expected / actual / match) run on the local build and again on the live URL. Never 'tests passed'.

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

Builds and debugs Playwright E2E suites. Use when authoring browser tests, fixing flakes, or hardening Playwright CI and locator strategy.

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

Guides user research and research ops. Use when running interviews, usability tests, surveys, or synthesis to de-risk product decisions; not experiments or review mining.

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

Designs risk-based test strategy for software delivery. Use when defining coverage, setting CI gates, managing flaky tests, choosing test layers, or establishing release criteria.

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

Designs performance and load testing: stress, spike, soak, capacity, CI budget gates. Use when planning load tests or perf gates; not code or SQL tuning.

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

Tests apps as an ICP persona through browser automation and reports friction, fixes, and risks. Use when running persona-based, ICP, or synthetic-user testing.

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

Tests whether changes caused a metric move without a clean A/B test: DiD, synthetic control, IV, RDD. Use when asking did a launch cause lift.

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

Tests whether data supports a claim: A/B significance, peeking, sample size, eval error bars, multiple comparisons. Use when deciding if results are significant.

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

Builds accessibility testing for WCAG 2.2 audits, CI gates, mobile audits, and EAA/ADA/VPAT evidence. Use when adding axe-core, Lighthouse, or screen-reader tests; not fixes.

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

Designs and tests distributed-system resilience. Use when adding retries, deadlines, hedging, circuit breakers, overload protection, chaos experiments, or SLO reliability gates.

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

Tests API contracts for REST, GraphQL, gRPC, AsyncAPI, and webhooks. Use when adding schema validation or breaking-change gates (Pact, can-i-deploy, oasdiff, buf); not API design.

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

Executes an approved implementation plan through fresh implementer and reviewer agents for each task, with explicit handoffs, focused tests, and task-by-task integration. Use for multi-task work where independent agent context improves implementation and review quality. Not for a single small edit, an unresolved design, or a failure that still needs root-cause analysis.

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

Implements behavior changes with a test-first red-green-refactor loop: write one meaningful failing test, watch it fail for the intended reason, make the smallest change, then refactor while green. Use for new behavior, bug fixes, refactors with preserved contracts, and regression tests. Not required for disposable prototypes, generated files, or documentation-only edits.

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

Designs and runs reproducible evaluations for AI agents, prompts, tools, skills, and model-backed workflows using realistic datasets, isolated baselines, objective assertions, rubric grading, trajectory analysis, cost/latency tracking, and regression comparison. Use when measuring agent quality, optimizing skill triggering, comparing prompts or models, or gating an AI feature release. Not for ordinary deterministic unit tests.

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

Maps an unfamiliar or large codebase before implementation by locating entry points, ownership, execution paths, conventions, tests, dependencies, change hotspots, and unresolved questions. Use when onboarding to a repository, scoping a cross-cutting change, preparing a handoff or reusable CodeTour, explaining a subsystem, or when the agent is guessing where behavior lives. Not for diagnosing one reproduced failure or designing a new architecture before the current system is understood.

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

Writes a detailed, executable implementation plan from an approved design or multi-step requirement, including exact files, interfaces, tests, commands, checkpoints, and rollback considerations. Use before touching code for a substantial feature, migration, refactor, or cross-cutting change. Not for a one-file bounded fix or for executing a plan that already exists.

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

Validates a running application, CLI, API, service, or generated artifact as a user or operator against a prewritten observable behavior contract while remaining source-blind. Use for acceptance checks, runtime proof, anti-fake probes, release smoke tests, or an independent companion to code review. Not for source-quality findings, root-cause diagnosis, or visual design judgment outside the contract.

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

Implement and route HitKeep contributions through the repository-owned hk developer platform. Use for any HitKeep code, UI, API, database, analytics-feature, seed, screenshot, documentation, integration, or release-preparation change, as well as setup, local development, builds, smoke tests, and contributor workflow discovery.

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

Generate engine-specific test helper libraries for the project's test suite. Reads existing test patterns and produces tests/helpers/ with assertion utilities, factory functions, and mock objects tailored to the project's systems. Reduces boilerplate in new test files.

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

Scaffold the test framework and CI/CD pipeline for the project's engine. Creates the tests/ directory structure, engine-specific test runner configuration, and GitHub Actions workflow. Run once during Technical Setup phase before the first sprint begins.

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

Detect non-deterministic (flaky) tests by reading CI run logs or test result history. Aggregates pass rates per test, identifies intermittent failures, recommends quarantine or fix, and maintains a flaky test registry. Best run during Polish phase or after multiple CI runs.

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

Improve a skill using a test-fix-retest loop. Runs static checks, proposes targeted fixes, rewrites the skill, re-tests, and keeps or reverts based on score change.

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

Generate a QA test plan for a sprint or feature. Reads GDDs and story files, classifies stories by test type (Logic/Integration/Visual/UI), and produces a structured test plan covering automated tests required, manual test cases, smoke test scope, and playtest sign-off requirements. Run before sprint begins or when starting a major feature.

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