Search Results for "coverage-report" | AgentCC

security-audit

Audit SkiaSharp's native dependencies for security vulnerabilities and CVEs. Read-only investigation that produces a status report with recommendations. Use when user asks to: - Audit security issues or CVEs - Check CVE status across dependencies - Find security-related issues and their PR coverage - Get an overview of open vulnerabilities - See what security work is pending Triggers: "security audit", "audit CVEs", "CVE status", "what security issues are open", "check vulnerability status", "security overview", "what CVEs need fixing". This skill is READ-ONLY. To actually fix issues, use the `native-dependency-update` skill.

differential-review

Performs security-focused differential review of code changes (PRs, commits, diffs). Adapts analysis depth to codebase size, uses git history for context, calculates blast radius, checks test coverage, and generates comprehensive markdown reports. Automatically detects and prevents security regressions.

analyzing-test-coverage

jeremylongshore

This skill analyzes code coverage metrics to identify untested code and generate comprehensive coverage reports. It is triggered when the user requests analysis of code coverage, identification of coverage gaps, or generation of coverage reports. The skill is best used to improve code quality by ensuring adequate test coverage and identifying areas for improvement. Use trigger terms like "analyze coverage", "code coverage report", "untested code", or the shortcut "cov".

generating-test-reports

Jeremylongshore Claude Code Plugins Plus Skills Test Report Generator

This skill generates comprehensive test reports with coverage metrics, trends, and stakeholder-friendly formats (HTML, PDF, JSON). It aggregates test results from various frameworks, calculates key metrics (coverage, pass rate, duration), and performs trend analysis. Use this skill when the user requests a test report, coverage analysis, failure analysis, or historical comparisons of test runs. Trigger terms include "test report", "coverage report", "testing trends", "failure analysis", and "historical test data".

coverage-report-analyzer

Jeremylongshore Claude Code Plugins Plus Skills Coverage Report Analyzer

Coverage Report Analyzer - Auto-activating skill for Test Automation. Triggers on: coverage report analyzer, coverage report analyzer Part of the Test Automation skill category.

qa-expert

This skill should be used when establishing comprehensive QA testing processes for any software project. Use when creating test strategies, writing test cases following Google Testing Standards, executing test plans, tracking bugs with P0-P4 classification, calculating quality metrics, or generating progress reports. Includes autonomous execution capability via master prompts and complete documentation templates for third-party QA team handoffs. Implements OWASP security testing and achieves 90% coverage targets.

crap-analysis

Analyze code coverage and CRAP (Change Risk Anti-Patterns) scores to identify high-risk code. Use OpenCover format with ReportGenerator for Risk Hotspots showing cyclomatic complexity and untested code paths.

Code Coverage Analysis

Multi-language code coverage analysis, reporting, and quality gate enforcement

media-monitoring

Deep integrations with media monitoring platforms for coverage tracking, sentiment analysis, and reporting

media-relations

Help users build relationships with journalists and get press coverage. Use when someone is pitching reporters, preparing for media outreach, trying to get press coverage, or managing ongoing journalist relationships.

bio-alignment-files-bam-statistics

Generate alignment statistics using samtools flagstat, stats, depth, and coverage. Use when assessing alignment quality, calculating coverage, or generating QC reports.

test-coverage

On-demand test coverage analysis. Use when identifying untested code, finding test gaps, measuring coverage metrics, or improving test quality. Trigger keywords - "test coverage", "coverage report", "untested code", "test gaps", "missing tests", "coverage metrics".

devtestingcoverage+2

pipeline-auditor

Audit/regression checks for the evidence-first survey pipeline: citation health, per-section coverage, placeholder leakage, and template repetition. **Trigger**: auditor, audit, regression test, quality report, 审计, 回归测试. **Use when**: `output/DRAFT.md` exists and you want a deterministic PASS/FAIL report before LaTeX/PDF. **Skip if**: you are still changing retrieval/outline/evidence packs heavily (audit later). **Network**: none. **Guardrail**: do not change content; only analyze and report.

outline-refiner

Planner-pass coverage + redundancy report for an outline+mapping, producing `outline/coverage_report.md` and `outline/outline_state.jsonl`. **Trigger**: planner, dynamic outline, outline refinement, coverage report, 大纲迭代, 覆盖率报告. **Use when**: you have `outline/outline.yml` + `outline/mapping.tsv` and want a verifiable, NO-PROSE planner pass before writing. **Skip if**: you don't want any outline/mapping diagnostics (or you have a frozen/approved structure and will not change it). **Network**: none. **Guardrail**: NO PROSE; do not invent papers; only report coverage/reuse and propose structural actions as bullets.

ln-782-test-runner

Executes all test suites and reports results with coverage

testing-coverage

Guide for writing tests and achieving high code coverage for CosmWasm contracts. Use when creating unit tests, integration tests, or analyzing coverage reports.

test-frontend-units

Executes frontend component unit tests for the Fake Survey Generator React application using Vitest. This skill validates that React components are properly tested and that existing tests continue to pass. Reports test failures and code coverage metrics.

test-backend-units

Executes backend unit tests and integration tests for the Fake Survey Generator project using TUnit framework. This skill validates that implemented features are covered by tests and that existing tests continue to pass. Reports test failures and code coverage metrics.

Test Coverage Gap Finder

Identify untested code paths, uncovered branches, and missing test scenarios using coverage analysis, risk mapping, and change-based coverage tracking

test-coveragecode-coveragebranch-coverage+4

Test Documentation Generator

Generating human-readable test documentation from test code including test catalogs, coverage reports, and living documentation websites.

documentationtest-catalogliving-docs+2

Bun Test Coverage

Use for test coverage with Bun, --coverage flag, lcov reports, thresholds, and CI integration.

post-dev-test

Post-development test completion. Use when: checking test coverage after feature-dev, writing missing integration/e2e tests. Not for: unit test generation (use codex-test-gen), test review (use test-review). Output: test files + coverage report.

test-review

Test coverage review via Codex MCP. Use when: reviewing test sufficiency, identifying coverage gaps, test quality audit. Not for: generating tests (use codex-test-gen), code review (use codex-code-review). Output: coverage analysis + gap report.

parallel-code-review

This skill should be used when performing comprehensive code reviews using multiple specialized review agents in parallel. It provides patterns for concurrent execution, decision tracking to prevent redundancy, and consolidated reporting. Use when needing thorough review coverage from multiple perspectives (security, architecture, performance) or when reviewing large changesets.

QA Engineering

World-class QA engineering — systematic testing, automation, and the mindset that finds bugs before users do. Use when "QA, quality assurance, testing, test automation, e2e tests, integration tests, regression testing, test coverage, Playwright, Cypress, Selenium, test suite, bug report, test strategy, flaky tests, testing, QA, automation, e2e, integration, regression, quality" mentioned.

testing

Testing commands and patterns for Oak AI project including running Jest unit tests, E2E tests with Playwright, coverage reports, and filtering tests. Use when writing tests, running test suites, or debugging test failures.

traceability-auditor

Validates complete requirements traceability across EARS requirements → design → tasks → code → tests. Trigger terms: traceability, requirements coverage, coverage matrix, traceability matrix, requirement mapping, test coverage, EARS coverage, requirements tracking, traceability audit, gap detection, orphaned requirements, untested code, coverage validation, traceability analysis. Enforces Constitutional Article V (Traceability Mandate) with comprehensive validation: - Requirement → Design mapping (100% coverage) - Design → Task mapping - Task → Code implementation mapping - Code → Test mapping (100% coverage) - Gap detection (orphaned requirements, untested code) - Coverage percentage reporting - Traceability matrix generation Use when: user needs traceability validation, coverage analysis, gap detection, or requirements tracking across the full development lifecycle.

test-coverage-analyzer

Analyzes test coverage reports, identifies gaps, and recommends priority areas for testing. Use when reviewing coverage, finding untested code, or planning test improvements.

speckit.tester

Execute tests, measure coverage, and report results.

coverage-analyzer

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

test-coverage

Generate comprehensive test coverage reports when reviewing code. Identifies untested code paths and low-coverage areas. Supports Python (pytest-cov), JavaScript (jest), Go (go test -cover), Java (JaCoCo). Use when reviewing tests or before approving code changes.

testgen

Generate tests using AI and run test suites. Use for generating unit tests, running coverage reports, and mutation testing.

pester

OleksandrKucherenko

PowerShell TDD testing framework guidance for Pester v5+. Use when writing, structuring, or debugging PowerShell unit tests; mocking cmdlets, native commands (bash, git, curl), or .NET types; isolating tests with TestDrive/TestRegistry; capturing output streams; generating code coverage or JUnit/NUnit reports for CI/CD; running parameterized or tagged tests; or troubleshooting Pester Discovery vs Run phase issues.

dotnet-testing-code-coverage-analysis

Comprehensive guide to code coverage analysis. Use when you need to analyze code coverage, generate coverage reports, or configure CI/CD coverage checks. Covers Coverlet configuration, report generation, interpreting metrics, and integration with cyclomatic complexity. Includes Fine Code Coverage, VS Code built-in tools, and best practices. Keywords: code coverage, coverage analysis, coverage report, Coverlet, Fine Code Coverage, dotnet-coverage, ReportGenerator, line coverage, branch coverage, cyclomatic complexity, runsettings, cobertura

shellspec

OleksandrKucherenko

A comprehensive unit testing framework for Bash and POSIX shell scripts that uses ShellSpec with TDD/BDD best practices. Use it when writing tests for shell scripts, diagnosing test failures, refactoring scripts for improved testability, setting up test infrastructure, mocking external dependencies, or adopting test-driven development for Bash/shell projects. Covers test structure, isolation, mocking, output capture, coverage reporting, CI integration, and troubleshooting.

sc-test

Execute tests with coverage analysis and automated quality reporting. Use when running unit tests, integration tests, e2e tests, analyzing coverage, or debugging test failures.

google-search-console

When the user wants to analyze Google Search Console data, use GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "title tag," "meta description," "GSC data analysis," "Search Console API," or "searchanalytics.query."

quality-coverage-report

HomericIntelligence

Generate test coverage reports showing which code paths are tested. Use to identify untested code and improve test coverage.

pytest-setup

Setup pytest with coverage reporting and watch mode for this Python project

audit

Comprehensive codebase audit with specialized reviewers. Generates actionable reports. Use when asked to "audit the codebase", "review code quality", "check for issues", "security review", or "performance audit". Accepts path scope like "apps/web". Reviewers run in batches of 2 by default to avoid resource exhaustion. Use --parallel to run all reviewers simultaneously (resource-intensive). Use --diff to scope audit to files changed vs main branch (or specify base: --diff develop). Use --docs for a focused JSDoc/documentation coverage audit. Use --copy for a focused UX writing/copy quality audit.

go-test

Go unit testing expert that helps generate test code, run tests, and produce coverage reports; supports ARM64 adaptive adjustments

cargo-llvm-cov

Code coverage for Rust using LLVM instrumentation with support for multiple output formats and CI integration. Use when measuring test coverage, generating coverage reports, enforcing coverage thresholds, or integrating with codecov/coveralls. Trigger terms: coverage, llvm-cov, code coverage, test coverage, coverage report, codecov, coveralls, branch coverage.

generating-test-reports

Generate comprehensive test reports with metrics, coverage, and visualizations. Use when performing specialized testing. Trigger with phrases like "generate test report", "create test documentation", or "show test metrics".

test-review

Dragonscale-Labs

Reviews test quality, coverage, and TDD compliance. Use when evaluating test suites, checking coverage reports, or ensuring tests follow best practices. Automatically activates when discussing tests, coverage, or test quality.

testing-workflow

Testing workflow patterns and quality standards. Activate when working with tests, test files, test directories, code quality tools, coverage reports, or testing tasks. Includes zero-warnings policy, targeted testing during development, mocking patterns, and best practices across languages.

skill-evaluator

Evaluate Claude Code skill quality across 6 weighted dimensions: frontmatter quality, trigger coverage, structural completeness, content depth, consistency and integrity, and CONTRIBUTING.md compliance. Produces scored audit reports with severity-classified findings and actionable recommendations. Two modes: (1) Quick Audit — single skill, full per-dimension report with weighted scoring; (2) Full Audit — all skills in repo, comparative ranking table plus per-skill summaries. Triggers on: "evaluate skill", "audit skill quality", "score skill", "skill review", "check skill completeness", "rate this skill", "skill quality check", "grade skill", "assess skill", "skill audit", "how good is this skill", or when a user asks for feedback on a SKILL.md file. Use this skill when reviewing skills before deployment, comparing skill quality across a repo, or diagnosing why a skill fails to activate on relevant queries.

validate-coverage-threshold

Validate test coverage meets minimum thresholds (default 80% overall, 80% statements, 75% branches, 80% functions). Parses coverage reports from coverage/coverage-summary.json or test output. Returns pass/fail status with detailed metrics and identifies uncovered files.

WebApp Testing

Automated UI testing for web applications using Playwright with comprehensive test coverage and reporting