299건 · 관련도순
Drive Keel agent test-first or evidence-first execution for a selected OpenSpec task. Use when a task needs software tests, hardware testbench, assertions, lint, new behavior proof, regression coverage, or red/green evidence before implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds, audits and packages Agent Skills, with their evals. Trigger to build, audit (security too), score or package a skill or SKILL.md; to design or integrate a pack; whether a skill beats incumbents; for trigger evals, test cases or assertion suites (skill, prompt card, agent spec); to slim a skill; when a skill did not fire or a run cost too much; for a prose pass on a skill's own files; to port or sanitize a skill set; to build or contract-test the MCP tools a plugin or mod ships; or say skillwright (evals, slim, diagnose, mcp, refresh, port, pack, integrate, upkeep). Prompt tuning is promptwright's; running a suite, claude plugin eval's; config slims, rigwright's; other docs, commscribe's; brands, brandscribe's; runtime grants, gatewarden's.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn vague Acceptance Criteria into measurable checks and test assertions
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Get best practices for MSTest 3.x/4.x unit testing, including modern assertion APIs and data-driven tests
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implements robust error handling in Ansible using block/rescue/always patterns, retry logic with until/retries, and clear assertion patterns for graceful failure management.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
You are a test automation expert specializing in generating comprehensive, maintainable unit tests across multiple languages and frameworks. Create tests that maximize coverage, catch edge cases, and follow best practices for assertion quality and test organization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Specialized skill for ASP.NET Core integration testing. Use when testing Web API endpoints, HTTP request/response, middleware, and dependency injection. Covers WebApplicationFactory, TestServer, HttpClient testing, in-memory database configuration. Keywords: integration testing, web api testing, WebApplicationFactory, TestServer, HttpClient testing, controller testing, endpoint testing, RESTful API testing, Microsoft.AspNetCore.Mvc.Testing, CreateClient, ConfigureWebHost, AwesomeAssertions.Web, Be200Ok, Be404NotFound, middleware testing, dependency injection testing
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Hunting skill for xxe vulnerabilities. Built from 10 public bug bounty reports including SVG-upload XXE, Office-doc (PPTX/DOCX) XXE, SOAP XXE, SAML AssertionConsumer XXE, blind OOB XXE via DTD callback, parameter-entity XXE, XXE-to-LFI, XXE-to-SSRF, and XXE-to-RCE chains (Adobe Commerce CosmicSting CVE-2024-34102). Use when hunting XXE on any target — emphasis on OOB-Or-It-Didn't-Happen Gate for blind cases.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
pytest + httpx + TestClient patterns for the FastAPI backend. Dependency overrides for auth, FakeSupabase mocking, HTTPException assertions. Use when writing or reviewing backend/tests/test_*.py.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.