1.6천건 · 관련도순
Show per-asset vuln-class coverage gaps for the active engagement so nothing in scope is skipped. Use when asked "coverage", "what haven't we tested", "test gaps", "are we thorough", or before calling an engagement done.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyzes test suites to identify redundant and duplicate test cases using coverage analysis, semantic similarity, and execution results. Use this skill when you need to reduce test suite size, identify redundant tests, optimize test execution time, analyze test coverage overlap, find tests with identical behavior, or improve test suite maintainability. Triggers when users ask to deduplicate tests, find redundant test cases, reduce test suite size, identify duplicate tests, or optimize test coverage.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Verify that design documents, code implementations, and tests fully cover all specified requirements. Use this skill when validating requirement traceability, conducting design reviews, assessing implementation completeness, checking test coverage against requirements, performing compliance audits, or identifying missing functionality. Produces coverage reports showing which requirements are satisfied, partially satisfied, or missing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automatically updates regression tests based on interval analysis to maintain coverage of key program intervals. Use when code changes affect value ranges, conditionals, or control flow, and existing tests need updating to maintain interval coverage. Analyzes interval information from updated code, identifies coverage gaps, adjusts test inputs and assertions, removes redundant tests, and generates new tests for uncovered intervals. Supports Python, Java, JavaScript, and C/C++ with various test frameworks (pytest, JUnit, Jest, Google Test).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for test coverage with Bun, --coverage flag, lcov reports, thresholds, and CI integration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enforces tiered test coverage standards with three dimensions — line coverage by tier, spec-to-test traceability, and spec-to-code implementation mapping. Use before claiming code is complete.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Suede AI eval design and coverage audit: AI-SPEC, failure-mode rubric with severity scoring, concrete pass/fail eval cases, coverage and infrastructure scores, and mechanical acceptance gates. Use when a change ships LLM, RAG, agent, classifier, prompt, or generated-media behavior, or when asked to write evals for an AI feature, design test cases for a model surface, audit existing eval coverage, or judge whether AI behavior is safe to ship. No AI-SPEC means no eval plan, and no eval plan holds the recommended ship verdict. NOT FOR: reviewing or grading the implementation code behind the AI surface (use suede-code); wiring a passing suite into CI as a required check (use suede-ci-gate); UAT of the built feature beyond the eval suite (a private Suede Labs companion, not in this pack).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Coverage-design method for qa-engineer — pyramid ratios per archetype, equivalence/boundary/property case selection, mutation score as the real coverage signal, and a flake-quarantine policy. Turns "coverage is 90%" (a number with no method) into a defensible test plan. Emits TEST-STRATEGY-{slug}.md, which the QA gate checks exists.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audits and enforces documentation quality. Use when checking coverage, freshness, runbook validity, AI-instruction coverage, or cleaning stale/duplicate markdown after LLM edits.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Takes a curriculum framework and a statutory or accreditation requirement list; produces a coverage table, gap summary, and CSV showing which framework content covers each requirement and where gaps exist.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Produces structured, citation-backed summaries of U.S. insurance policies, endorsements, claims files, and coverage correspondence for coverage analysis and insurance litigation. Use when summarizing policies, declarations, claims files, reservation-of-rights letters, denial letters, or coverage disputes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Provides information about insurance coverage options and details.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates structured summaries of U.S. insurance claim files covering identification, incident narrative, party positions, coverage analysis, and resolution status. Use when synthesizing claim files for adjusters, legal counsel, or claims managers during pre-filing review, discovery, or settlement preparation. Trigger keywords: claim summary, insurance claim, coverage summary, adjuster summary, coverage denial, reservation of rights.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Produces structured summaries of insurance claims correspondence including coverage letters, reservation of rights (ROR), denial letters, and claim file documents. Extracts policy details, coverage positions, claims chronology, settlement posture, and liability exposure. Use when summarizing claim files, coverage disputes, ROR letters, denial letters, or multi-document insurance correspondence threads.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Identify coverage gaps in existing insurance portfolios. TRIGGERS - Use when user needs help with coverage-gap-finder related tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drafts structured insurance coverage opinions analyzing duty to defend and duty to indemnify for carriers. Applies eight corners rule, policy exclusion analysis, and state-specific law. Use when a carrier receives a claim or lawsuit, needs a coverage determination, reservation of rights analysis, or defense obligation assessment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Verifies provider credentials via NPI MCP, searches Medicare coverage policies via CMS Coverage MCP, and maps clinical evidence to policy criteria with MET/NOT_MET/INSUFFICIENT assessment, per-criterion confidence scoring, and documentation gap analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit existing security controls and detection coverage — find gaps against MITRE ATT&CK. Use when asked to "audit our detection coverage", "where are our security control gaps", or "check our MITRE coverage".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when reviewing, shipping, or regression-testing a SKILL.md and you hold one or more captured trajectories where that skill was actually loaded. Translates the skill's instructions into behavior constraints, then reports which were EXERCISED (coverage) versus untested, and flags any that were in-scope but VIOLATED (compliance) — a cheap single-trajectory test-adequacy gate. It surfaces untested instructions rather than auto-blocking, and escalates fail-closed only when a violation touches shared repo state, never-surface memory, or self-modification. Complements skill-counterfactual-audit (which measures EFFECT) and skill-causal-curation (which measures contribution); this one asks ADEQUACY. Backed by the agent-skill-coverage metric (arxiv 2606.20659v2). Triggers on skill review, ship gating, and regression-testing a skill against its trajectories.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Check agent configuration coverage across hierarchy levels and phases. Use to ensure complete agent system coverage.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drive a PR to a green quality gate and keep it there. Loops on SonarCloud for the project's targets, no new issues, no duplication on new code, and coverage on new logic as close to 100% as the code allows, then watches the PR checks until every one passes. Use when a quality gate blocks a merge, when coverage or duplication has to come up, or before asking for review. Triggers - "fix the sonar issues", "quality gate", "get coverage up", "zero duplication", "loop until CI is green", "watch the checks".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write focused tdmcp tests for one assigned coverage gap. Use for Vitest/msw unit tests, integration tests, bridge tests, CLI/config/resource tests, and regression tests that should raise coverage without weakening behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detect missing docs, undocumented files, project health issues, and coverage gaps on session start or on-demand. Scans for README gaps, TODO/FIXME counts, and test coverage holes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a user needs to measure fuzz corpus coverage, explain a coverage plateau, or turn uncovered regions into campaign work. Not for harness creation: use fuzz-harness-writing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.