'coverage' 검색 결과

Use when writing, generating, or improving Pest tests for Laravel — clear intent, good coverage, maintainable structure, and alignment with project testing conventions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when designing or auditing a sales pipeline — stage exit criteria, per-cell conversion, coverage reasoning, leak detection. Triggers on 'tighten our pipeline', 'where is the leak'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a diff may lack tests — missing assertions, uncovered branches, over-mocking, no regression test for a bug fix — dispatched by /review-changes, /do-and-judge, /judge, even without 'tests'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when polishing a skill/rule/command/guideline frontmatter description — pushier phrasing, trigger coverage, undertrigger audit — even if the user just says 'make this pushier'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review a written plan or design doc through a designer's lens before implementation - seven passes over information architecture, interaction states, emotional arc, AI-slop risk, design-system alignment, responsive and accessibility coverage, and unresolved decisions. Each dimension is rated 0-10 with an explicit statement of what would make it a 10, then the plan is edited to get there. Use when a plan has a UI surface and you want the design gaps closed before code is written. Not for auditing a live site.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

QA engineer for test automation and coverage. Use when the user asks to talk to Quinn or requests the QA engineer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

[Implementation] Use when a workflow step or the user asks for root-cause fixes with regression coverage. --target={ci|issue|logs|review|test|types|ui} scopes the issue.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Fan out N independent workers, collect their results, and return one report for coverage, races, gauntlets, or exploration.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Plan, write, and maintain automated tests in any language, with worked examples in Python and JavaScript/TypeScript. Use this skill whenever the user wants to write or plan tests, apply TDD (red-green-refactor), structure unit tests with arrange-act-assert and given-when-then naming, choose between fakes, stubs, and mocks, set up dependency injection for testability, build integration tests with testcontainers, database seeding, or transaction rollback, write Playwright or Cypress end-to-end tests, use property-based testing with Hypothesis or fast-check, create pytest fixtures or factory_boy factories, review coverage or mutation testing, or triage flaky tests in CI. Also trigger for "test pyramid", "test trophy", "test isolation", "mocking", "snapshot tests", "golden files", "parametrized tests", "make the tests pass".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks to verify a story or ticket implementation against its spec - per-AC verdicts, code reuse and design conformance, dead code, then adversarial maintainer verification. Requires the qa/review agent roles registered by scripts/install-codex.sh. Keywords: story QA, acceptance criteria, spec conformance, AC coverage, QA this branch, verify story.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when adding a test to an existing codebase for behavior that is already implemented. Ensures the test is meaningful by mutation-verifying it — breaking the production code to confirm the test fails for the expected reason. Triggers when the user says "add a test for existing behavior", "backfill test coverage", "the test passes on first run", or any scenario where a test is written without a corresponding new production change.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when modifying, removing, or refactoring code that lacks test coverage. Emphasizes the danger of untested changes and the RGR workflow to add characterization tests before modifications.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

TDD Production Code Refactoring Process. Triggers on 'tidy up', 'tidy this', 'clean up code'. Use for refactoring production code with test coverage.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Refactor test files to improve behavioral coverage, clarity, structure, assertions, fixture setup, mocking strategy, and remove implementation-detail or low-value tests. Use when asked to clean up, declutter, consolidate, or improve tests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when implementing a new function, adding a feature, fixing a bug, refactoring with test coverage, or writing a new test. Enforces strict outside-in red-green-refactor TDD with one-failure-per-turn discipline, predict-the-failure-before-every-run checks, hardcode-first minimum changes, triangulation, and property-based testing for large input spaces. Triggers on explicit TDD requests and on any task phrased as "implement", "add", "write a function", "build a feature", or "fix a bug" in a test-capable codebase. Reports red/green validation evidence.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Validate, migrate, and atomically persist files and configuration with safe fallback and restart coverage.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implement minimal network events and component state with authority, conversion, dirtying, and regression coverage.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reproduce failures, trace authoritative flow, prove the broken assumption, and add targeted regression coverage.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Virtual QA Lead that turns requirements into review-ready, TestRail-importable test cases in one conversation. Use it whenever the user has requirements, a spec, a user story, or acceptance criteria (PDF, DOCX, XLSX, TXT, MD, or pasted text) and wants test cases, a test plan, a checklist, test coverage, a regression suite, or a TestRail/Qase/Zephyr export, even without saying "test cases" ("write tests for this spec", "what should we check here?"). Especially useful when they attach their team's existing test cases to match. When the spec describes an API (endpoints, status codes, schemas, auth, OpenAPI/Swagger), Casely also builds a runnable Postman collection, so use it for "API tests", "Postman collection", or "tests I can run in Newman/CI". Triggers on the same request in any language.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Phase 5 part of disease-market-sizing-orchestration. Injects consulting palette (navy/gold/blue) + base CSS + floating TOC + section dividers into raw report HTML. Validates token coverage ≥60% (warn) and floating TOC li ≥5 (block). Use AFTER content-verification passes, BEFORE report-bundle-builder build_all_deliverables.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

You are a senior test engineer. Auto-detect all test layers (unit, integration, frontend, backend, E2E/system), run them all, write more if coverage is below threshold, and loop until everything passes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run the pre-commit quality gate: test coverage, security scan, local build, plus Docker and cloud checks when applicable. Use before any commit or push; a failing gate blocks both.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Creates an integration testing plan for .NET data access artifacts during Oracle-to-PostgreSQL database migrations. Analyzes a single project to identify repositories, DAOs, and service layers that interact with the database, then produces a structured testing plan. Use when planning integration test coverage for a migrated project, identifying which data access methods need tests, or preparing for Oracle-to-PostgreSQL migration validation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.