299건 · 관련도순
Write and improve Playwright tests for browser workflows, APIs, components, visual changes, and accessibility. Provides TypeScript and JavaScript patterns for selecting elements, waiting reliably, managing authentication and test data, and investigating intermittent failures.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review new and existing tests for meaningful behavior coverage, duplication, and dependence on implementation details. Gather evidence before cleanup, preserve tests that protect independent contracts, and verify that removed tests leave their regression checks covered elsewhere.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Checks whether work is truly complete before reporting success, committing changes, or creating a pull request. It runs the relevant checks, reads their full output, and ties status reports to current evidence.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Comprehensive guide to stretchr/testify for Golang testing. Covers assert, require, mock, and suite packages in depth. Use when writing tests with testify, creating mocks, setting up test suites, or choosing between assert and require. Covers testify assertions, mock expectations, argument matchers, call verification, suite lifecycle, and advanced patterns like Eventually, JSONEq, and custom matchers. Apply when the codebase imports github.com/stretchr/testify.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[omh] Testing an internal control -- SOX, ICFR or ITGC: define the population and the sample, name the evidence that proves each item, re-perform the control, and grade any deficiency from stated likelihood, magnitude and compensating-control criteria, never by assertion. Use when the user says: internal-audit, internal audit, internal control, internal controls, internal control audit, control testing, test of controls, tests of controls.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', reviewing a small diff you don't trust, or a brief that asserts something about existing code ('make X public', 'X already handles Y') before you design against that assertion.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Connects AI agents to remote Windows desktop applications on Amazon WorkSpaces Applications (AppStream 2.0) through the managed Agent Access MCP server, and guides reliable desktop automation. Covers connecting an agent to the MCP endpoint (SigV4, streaming URL, and Active Directory SAML/Domain Join), BLOCKING vs POLLING connect modes, the computer-use tools (screenshot, click, type, key, scroll), screenshot-budget and action-batching discipline, MCP tool forwarding (forwarded___ tools), session lifecycle and expire-on-delete, and troubleshooting connection errors. Use when building or debugging an agent that drives a remote Windows desktop or GUI application via WorkSpaces Applications / AppStream — including "dcv session not ready", "client_disconnected", 400 signing-region, POLLING/connection_status, SAML assertion, or forwarded tool questions. Not for Amazon WorkSpaces Personal/Core virtual desktops or general AppStream fleet administration unrelated to agent access.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deploy an Alchemy-backed service through environment-scoped credentials, chain assertions, canaries, and rollback gates. Use when promoting an integration to hosted environments. Trigger with "deploy Alchemy integration", "Alchemy production deploy", or "promote an Alchemy service".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Verifies whether a scientific or biomedical claim is actually supported by the cited original papers rather than by citation drift, overstatement, selective citation, or correlation-to-causation inflation. Use this skill whenever a user wants to check whether a repeated statement, slide claim, manuscript sentence, review assertion, or “people often say” scientific conclusion is truly supported by the underlying primary literature. Always separate the claim itself, the cited paper(s), what the paper actually showed, what it did not show, and whether later retellings drifted beyond the original evidence. Never fabricate references, findings, study features, or citation chains.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate BATS test structure and fixtures for shell script testing with setup/teardown, assertions, and mocking.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up E2E test harness for CLI applications with process spawning and assertions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs. Evidence before assertions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run GDScript test suites from the command line with `godot --headless`, using a SceneTree/MainLoop runner script that exits non-zero on failure so CI can gate merges. Use when a Godot project needs unit tests without opening the editor, when wiring a CI job (GitHub Actions or similar) that must fail the build on a failing `.gd` test, or when a `godot --headless` invocation hangs, opens a window, or exits 0 despite failed assertions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews test code to identify and fix common testing anti-patterns including flaky tests, over-mocking, brittle assertions, test interdependency, and hidden test logic. Flags bad patterns, explains the specific defect, and provides corrected implementations. Use when reviewing test code, debugging intermittent or unreliable test failures, or when the user mentions flaky tests, test smells, brittle tests, test isolation issues, mock overuse, slow tests, or test maintenance problems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Applies proven testing patterns — Arrange-Act-Assert (AAA), Given-When-Then, Test Data Builders, Object Mother, parameterized tests, fixtures, spies, and test doubles — to help write maintainable, reliable, and readable test suites. Use when the user asks about writing unit tests, integration tests, or end-to-end tests; structuring test cases or test suites; applying TDD or BDD practices; working with mocks, stubs, spies, or fakes; improving test coverage or reducing flakiness; or needs guidance on test organization, naming conventions, or assertions in frameworks like Jest, Vitest, pytest, or similar.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Configures and runs LLM evaluation using Promptfoo framework. Use when setting up prompt testing, creating evaluation configs (promptfooconfig.yaml), writing Python custom assertions, implementing llm-rubric for LLM-as-judge, or managing few-shot examples in prompts. Triggers on keywords like "promptfoo", "eval", "LLM evaluation", "prompt testing", or "model comparison".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Bridges Claude Code and Codex sessions when native tools can't reach the target. Use for 跨产品通信 / 脚本回帖 / 送达排查: cross-product messages, hooks or scripts posting to a session, verifying delivery (Held messages included), shared-work ownership, or an inbound peer assertion. Not for same-product or parent/subagent messaging (use native tools), spawning agents, moving full history, or cross-machine pairing (deprecated).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design assertions that prove the actual contract and fail on realistic regressions
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Gates whether a new test should exist and forces it to be efficient, protecting CI from low-value test bloat. Use before any change to what a pytest, Jest, or Playwright test asserts or sets up, down to one fixture or one assertion added to an existing block. Front-loads the value bar (every test must catch a realistic regression no existing test already catches; extend the nearest existing test before writing a new standalone one; test behavior through the public interface, not implementation details; collapse near-duplicates into parameterized cases) and the efficiency bar (deterministic, isolated, fast; pick the cheapest test level; Django TestCase over TransactionTestCase; no sleeps, no real network; no time bombs from absolute dates left to age against the real clock; no database a test never uses). Includes a "don't write it" decision tree. For fixing an existing flaky test use `/fixing-flaky-tests`; after this gate says a Playwright test is warranted, use `/playwright-test` for mechanics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Records visual proof while testing UI behavior — the agent tests the app hands-on via computer use while a screen recording with structured test/assertion annotations captures the session — then posts the video and a results summary to the requested destination. Use when changed runtime behavior needs observable verification, including headless environments (scripted screenshots and probes) and non-UI changes (measured numbers, output pairs).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up an end-to-end test suite in any repo, following practices that make e2e a reliable per-PR gate: real flows over bypass, layered assertions, a reusable auth/session helper, video+trace evidence, and a compounding suite. Use when a repo has no e2e (or weak e2e) and you want system-level tests — "set up e2e", "add end-to-end tests", "scaffold a test gate".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Convert English-language properties in PROPERTIES.md (produced by the Fizz skill) into Solidity assertions inside the existing fuzz harness, then flip their checkboxes. Trigger on "fizz-convert", "convert properties", "implement properties from PROPERTIES.md", "convert PROPERTIES.md to Solidity".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.