Results for “coverage”

Analyze existing test suites and source code to suggest additional unit tests that improve test coverage. Use this skill when working with test files and source code to identify untested code paths, missing edge cases, uncovered branches, untested error conditions, and gaps in test coverage. Supports major testing frameworks (pytest, Jest, JUnit, Go testing, etc.) and generates targeted test suggestions based on coverage analysis.

The English summary is being prepared. Showing the original description.

Define, track, and act on QA metrics: test coverage percentage, flakiness rate, defect escape rate, MTTR, test execution time trends, automation ROI, quality gates, and SLAs for test suites. Includes metric formulas, realistic targets by company stage, and the action to take when each metric goes red. Use when: "QA metrics," "test metrics," "quality KPIs," "test health," "flakiness rate," "defect escape rate." Not for: building the dashboard UI (Allure/Grafana) — use qa-dashboard; measuring coverage gaps and mutation score — use coverage-analysis. Related: qa-dashboard, coverage-analysis, ci-cd-integration, release-readiness, quality-postmortem.

The English summary is being prepared. Showing the original description.

Generate Coverage and insurance resources with payer diversity including Medicare, Medicaid, commercial, Tricare, VA, and self-pay. Use when user mentions coverage, insurance, payer, Medicare, Medicaid, benefits, or coordination of benefits. For claims and EOB see the claims-eob skill.

The English summary is being prepared. Showing the original description.

解析 Verilator coverage.dat + sim log，输出 functional + code coverage 数值，判断是否 100% 达标。触发场景：(1) bb-invoke-verilator 后；(2) 每次回归后；(3) 显式 /bb-collect-coverage。

The English summary is being prepared. Showing the original description.

Calculates CRAP (Change Risk Anti-Patterns) score for .NET methods, classes, or files. Use when the user asks to assess test quality, identify risky untested code, compute CRAP scores, or evaluate whether complex methods have sufficient test coverage. Requires code coverage data (Cobertura XML) and cyclomatic complexity analysis. DO NOT USE FOR: writing tests, general test execution unrelated to coverage/CRAP analysis, or general code coverage reporting without CRAP context.

The English summary is being prepared. Showing the original description.

Analyze test coverage with detailed metrics, identify gaps, and generate comprehensive reports. Use when measuring code coverage, finding untested code, or validating coverage thresholds.

The English summary is being prepared. Showing the original description.

Validates detection coverage by mapping Atomic Red Team tests to ATT&CK techniques, checking which of your detections cover each tested technique, and reporting coverage gaps. Activates for requests to validate detections with atomic tests, map Atomic Red Team to coverage, or find detection gaps against tested techniques.

The English summary is being prepared. Showing the original description.

Maps hunts and detections to MITRE ATT&CK for coverage analysis: tagging hypotheses with techniques, building a coverage matrix from completed hunts, and identifying high-risk gaps to prioritize next. Activates for requests to map hunts to ATT&CK, build a coverage heatmap, or find detection gaps by technique.

The English summary is being prepared. Showing the original description.

Create QA test strategy documents, coverage matrices, and risk-based test prioritization plans. Use this skill whenever a QA lead or manager needs to plan what to test, why, and at what depth. Trigger on phrases like "write a test strategy", "test strategy document", "what should we test", "prioritize testing", "risk-based testing", "test coverage plan", "QA approach for this project", "coverage matrix", "test scope", "how should we approach testing this quarter", "where are our coverage gaps", or any request to define the strategic plan for testing - not the execution of it. Also trigger at project kickoff when a QA lead asks "how do we approach quality on this?"

The English summary is being prepared. Showing the original description.

Comprehensive test suite review across five phases. Surveys unit coverage, integration coverage, E2E (browser) coverage for webapps, fuzz coverage, and test quality — in that order. Advisory only — produces findings and proposes tickets; does not implement test changes.

The English summary is being prepared. Showing the original description.

An innate exploratory drive that guarantees no graph node remains permanently invisible to an agent population. After a warm-up period (step > 3), each agent fires a coverage scan with probability |unseen_nodes| / |all_nodes|. When triggered, the agent teleports directly to the globally unseen node with the highest belief uncertainty, works it, and returns control to the normal action-selection loop. Probability is self-annealing: it starts near 1.0 when almost everything is unseen and decays toward 0.0 as coverage saturates, requiring no manual schedule. The mechanism is "innate" (hard-coded into the agent step loop) as distinct from the "adaptive" EFE path, which requires local neighbors and learned precision weights. Together they form a two-layer exploration architecture: adaptive for locally-guided foraging, innate for topological completeness.

The English summary is being prepared. Showing the original description.

Run pytest tests with coverage, discover lines missing coverage, and increase coverage to 100%.

The English summary is being prepared. Showing the original description.

Coverage review and verification sufficiency routing. Use when test coverage, uncovered paths, coverage reports, or verification adequacy need a read-only QA review; do not use for writing tests or running browser/E2E artifacts.

The English summary is being prepared. Showing the original description.

Measure and improve OpenClaw test and plugin-suite performance by investigating slow imports, repeated startup work, and memory use. Compare results before and after changes while preserving test coverage and verifying the affected tests.

• Finding slow tests and expensive module imports
• Reducing plugin-suite runtime and memory use
• Investigating growing memory use during tests

Check a Laravel project before merging or deploying. Work through environment settings, code checks, tests and coverage, dependency security, database changes, caches, queues, and scheduled tasks, stopping when a required check fails.

• Checking a Laravel project before opening a pull request
• Verifying a major refactor or dependency upgrade
• Checking readiness for staging or production deployment

Write Kotlin tests with Kotest and MockK using test-driven development, where tests come before implementation. Cover asynchronous code, check behavior across generated inputs, and use Kover reports to measure how much code the tests exercise.

• Adding tests to existing Kotlin code
• Developing new functions by writing tests first
• Testing coroutines and Flow behavior

Build Laravel features test first with PHPUnit or Pest. Create tests for models, HTTP endpoints, authentication, and permissions, simulate external services, and measure coverage to see which code your tests exercise.

• Building Laravel features test first
• Testing API authentication and permissions
• Simulating payments, mail, and queues in tests

Helps build Go tests using a test-first workflow. Covers grouped test cases, HTTP response checks, performance benchmarks, fuzzing to explore generated inputs, and coverage reports showing which code was exercised by tests.

• Developing Go functions with tests written first
• Adding normal and error cases to existing tests
• Measuring execution time and memory allocations

Check a Django application before a pull request or deployment. Review its environment, code quality, database changes, tests, vulnerabilities, and configuration, then produce a phased pass/fail report identifying issues that need fixes.

• Checking a Django pull request
• Reviewing database migrations
• Checking test coverage targets

Define project quality standards in CONSTRAINTS.md, connect measurable targets to checks, and inspect changes for weakened safeguards. It helps teams choose thresholds and catch skipped tests, suppressed warnings, unfinished code, or lowered standards during agent development.

• Set quality standards before starting agent development
• Choose coverage and performance thresholds
• Detect skipped tests and suppressed warnings

Audit a test suite to identify redundant tests, empty checks, and tests tied to internal implementation. Consolidate or remove them with evidence while preserving useful checks that detect regressions, meaning previously fixed problems returning.

• Audit duplicate test coverage
• Prune tests while preserving regression detection
• Review tests tied to internal implementation

Review mobile test coverage across real devices and simulated screen sizes. Find gaps in automated checks and CI, the workflow that runs project checks, and add Playwright tests for key mobile user flows.

• Reviewing mobile test coverage in CI
• Adding Playwright tests for mobile user flows
• Planning Android and iOS real-device checks

Audit whether a website serves all pages over HTTPS with valid TLS certificates, which secure connections. Check certificate coverage and expiration, permanent redirects from HTTP, and HTTPS URLs for internal links and resources, then review the necessary configuration changes.

• Auditing HTTPS coverage across a website
• Checking certificate expiration and hostname coverage
• Verifying permanent redirects from HTTP to HTTPS

Review and add E2E tests, which check complete user journeys such as signing in or checking out. Identify missing coverage, organize reusable tests, and check that automated delivery workflows run them and handle failures.

• Checking test coverage for sign-in and checkout flows
• Adding tests for form submissions
• Reviewing automated test runs and failure handling in CI/CD