'coverage' 검색 결과

Mandatory final risk-focused review for any repository change. Checks security, architecture boundaries, test coverage, and release readiness before closeout.

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

Design, implement, and stabilize automated tests in this repository (unit, integration, and E2E) for .NET/C#, Rust, APIs, and frontend flows. Use when the user asks to create tests, increase coverage, fix flaky tests, or validate behavior changes.

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

Design and implement observability and SRE controls including SLO/SLI, OpenTelemetry instrumentation, alerting, dashboards, and incident readiness. Use when tasks involve telemetry coverage, operational reliability metrics, incident response, or runbook quality.

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

Implement, organize, and test Rust modules in this repository following mandatory project organization and test discovery rules. Use when tasks involve Cargo crates, module structure, Rust refactors, or creation/fix of Rust tests including required error test coverage.

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

Implement, organize, and test Rust modules following mandatory project organization and test discovery rules. Use when tasks involve Cargo crates, module structure, Rust refactors, or creation/fix of Rust tests including required error test coverage.

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

Design, implement, and stabilize automated tests (unit, integration, E2E) for .NET/C#, Rust, APIs, and frontend flows. Use when the user asks to create tests, increase coverage, fix flaky tests, or validate behavior changes.

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

Unit and integration testing strategy. USE FOR: writing tests; coverage improvements; vitest specs; test refactoring. DO NOT USE FOR: production code changes (use code-implementation skill); documentation (use documentation skill); commits (use commit-conventions skill).

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

Unit and integration testing strategy for create-vue-dsfr. Use for writing, updating, or refactoring Vitest specs and test coverage. Read the shared project skill before acting.

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

Retroactively audit an executed AI phase's evaluation coverage — scores each eval dimension as COVERED/PARTIAL/MISSING and produces an actionable EVAL-REVIEW.md with remediation plan

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

Deploys and configures CrowdStrike Falcon EDR agents across enterprise endpoints to enable real-time threat detection, behavioral analysis, and automated response. Use when onboarding endpoints to EDR coverage, configuring detection policies, or integrating Falcon telemetry with SIEM platforms. Activates for requests involving CrowdStrike deployment, Falcon sensor installation, EDR policy configuration, or endpoint detection and response.

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

Builds SOC performance metrics and KPI tracking dashboards measuring Mean Time to Detect (MTTD), Mean Time to Respond (MTTR), alert quality ratios, analyst productivity, and detection coverage using SIEM data. Use when SOC leadership needs operational visibility, continuous improvement tracking, or executive-level reporting on security operations effectiveness.

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

Generate and run tests for Adobe App Builder actions and UI components. Scaffolds Jest unit tests, integration tests against deployed actions, contract tests for Adobe API interactions, and React component tests using Testing Library. Provides mock helpers for State, Files, Events SDKs, @adobe/aio-lib-* clients, ExC Shell context (@adobe/exc-app), and UIX Guest SDK (@adobe/uix-guest). Use this skill whenever the user mentions testing App Builder actions, writing unit tests for Runtime actions, creating integration tests, mocking Adobe SDKs, setting up test fixtures, running aio app test, or wants to verify action behavior before deployment. Also trigger when users mention Jest configuration for App Builder, test coverage, CI test setup, React component test, Testing Library, UI test, Provider wrapper, test my page, test my form, test my table, test my component, mock shell context, mock extension context, debug test failures, or fix Jest errors.

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

Write, run, and maintain tests using Vitest with proper isolation patterns and coverage targets.

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

Creates comprehensive permission tests ensuring RBAC doesn't regress with test matrices, CI gating, and authorization coverage. Use for "RBAC testing", "permission tests", "authorization testing", or "access control tests".

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

Enforces minimum quality thresholds in CI including code coverage, linting, type checking, and security scanning. Provides required checks, PR rules, and automated enforcement. Use for "quality gates", "CI checks", "code quality", or "PR requirements".

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

Generates comprehensive API test suites using Jest, Vitest, or Supertest from Express, Next.js, Fastify, or other API routes. Creates integration tests, contract tests, and edge case coverage. Use when users request "generate api tests", "create endpoint tests", "api test suite", or "integration tests for api".

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

Use for the search-planning stage of a literature review, when database lanes and language layers must be chosen, when DOI coverage policy is unclear, or when inclusion and exclusion criteria need drafting before any source is read; not for running the screening and PRISMA pipeline of a formal review, which is prisma-scoping-review-pipeline.

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

Use when paired tr.md and en.md files need a parity verdict, when titles, frontmatter, headings, or DOI sets may have drifted between languages, or when a bilingual document is approaching release and its translation coverage needs an audit.

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

This skill should be used when the user asks for "browser tests", "playwright tests", "end-to-end testing", "test user flows", "E2E coverage", "integration tests for UI", "page object pattern", "/e2e command", or discusses automated browser testing. Covers the E2E test loop workflow, Playwright patterns, page objects, and selector strategies.

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

| Type | Coverage | Speed | Tools |

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

Week 2 of the exploit development curriculum. Covers fuzzing methodology: target selection, corpus generation, coverage-guided fuzzing with AFL++/libFuzzer, structured fuzzing, and triage/deduplication. Use when setting up fuzz campaigns, selecting harness strategies, or triaging fuzzer output.

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

Enterprise-grade code review agent. Reviews PRs, diffs, or code files for security vulnerabilities, performance issues, error handling gaps, architecture smells, and test coverage. Works with any language, any repo, no dependencies required.

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