Token导航 LogoToken导航TokenDH.com
研究检索执行命令github未标认证来源可访问许可证需确认审计提醒

configure-coverage配置覆盖范围

Agent Skill

configure-coverage 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

1,335

周安装

54

GitHub Stars

28

下载量

419
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:configure-coverage(配置覆盖范围)
来源仓库:https://github.com/laurigates/claude-plugins
仓库路径:skills/configure-coverage
安装命令:
npx skills add https://github.com/laurigates/claude-plugins --skill configure-coverage
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/laurigates/claude-plugins --skill configure-coverage

简介

configure-coverage 用于配置代码覆盖率阈值与报告机制,支持 Vitest、Jest、pytest 和 Rust 等框架。

  • 适用于测试流程中的覆盖率监控与质量门禁设置。
  • 可集成 Codecov 或 Coveralls 实现持续反馈。
  • 包含命令行操作,需谨慎评估其对现有测试流程的干扰。
  • 推荐在非高峰时段运行以避免影响开发效率。

SKILL.md

/configure:coverage

Check and configure code coverage thresholds and reporting for test frameworks.

When to Use This Skill

Use this skill when...Use another approach when...
Setting up coverage thresholds for Vitest, Jest, pytest, or RustRunning tests with coverage (/test:coverage)
Configuring coverage reporters (text, JSON, HTML, lcov)Configuring the test framework itself (/configure:tests)
Adding Codecov or Coveralls integration to CI/CDAnalyzing test failures (test-runner agent)
Auditing coverage configuration compliance across a projectWriting individual test cases
Adjusting coverage threshold percentagesConfiguring general CI/CD workflows (/configure:workflows)

Context

  • Project root:!pwd
  • Package files:!find. -maxdepth 1 \(-name 'package.json' -o -name 'pyproject.toml' -o -name 'Cargo.toml' \)
  • Vitest config:!find. -maxdepth 1 -name 'vitest.config.*'
  • Jest config:!find. -maxdepth 1 -name 'jest.config.*'
  • Coverage dir:!find. -maxdepth 1 -type d -name 'coverage'
  • Codecov config:!find. -maxdepth 1 \(-name 'codecov.yml' -o -name '.codecov.yml' \)
  • Project standards:!find. -maxdepth 1 -name '.project-standards.yaml'

Parameters

Parse from command arguments:

  • --check-only: Report compliance status without modifications (CI/CD mode)
  • --fix: Apply fixes automatically without prompting
  • --threshold <percentage>: Set coverage threshold (default: 80)

Default threshold: 80% (lines, branches, functions, statements)

Supported frameworks:

  • Vitest: @vitest/coverage-v8 or @vitest/coverage-istanbul
  • Jest: Built-in coverage with --coverage
  • pytest: pytest-cov plugin
  • Rust: cargo-llvm-cov or cargo-tarpaulin

Execution

Execute this code coverage compliance check:

Step 1: Detect test framework and coverage configuration

Check for framework indicators:

IndicatorFrameworkCoverage Tool
vitest.config.* with coverageVitest@vitest/coverage-v8
jest.config.* with coverageJestBuilt-in
pyproject.toml [tool.coverage]pytestpytest-cov
.cargo/config.toml with coverageRustcargo-llvm-cov

Use WebSearch or WebFetch to verify latest versions of coverage tools before configuring.

Step 2: Analyze current coverage state

For the detected framework, check configuration completeness:

Vitest:

  • Coverage provider configured (v8 or istanbul)
  • Coverage reporters configured (text, json, html, lcov)
  • Thresholds set for lines, functions, branches, statements
  • Exclusions configured (node_modules, dist, tests, config files)
  • Output directory specified

Jest:

  • collectCoverage enabled
  • coverageProvider set (v8 or babel)
  • collectCoverageFrom patterns configured
  • coverageThresholds configured
  • coverageReporters configured

pytest:

  • pytest-cov installed
  • [tool.coverage.run] section exists
  • [tool.coverage.report] section exists
  • Coverage threshold configured (--cov-fail-under)

Rust (cargo-llvm-cov):

  • cargo-llvm-cov installed
  • Coverage configuration in workspace
  • HTML/LCOV output configured

Step 3: Generate compliance report

Print a formatted compliance report:

Code Coverage Compliance Report
================================
Project: [name]
Framework: [Vitest 2.x | pytest 8.x | cargo-llvm-cov 0.6.x]

Coverage Configuration:
  Provider                @vitest/coverage-v8        [CONFIGURED | MISSING]
  Reporters               text, json, html, lcov     [ALL | PARTIAL]
  Output directory        coverage/                  [CONFIGURED | DEFAULT]
  Exclusions              node_modules, dist, tests  [CONFIGURED | INCOMPLETE]

Thresholds:
  Lines                   80%                        [PASS | LOW | NOT SET]
  Branches                80%                        [PASS | LOW | NOT SET]
  Functions               80%                        [PASS | LOW | NOT SET]
  Statements              80%                        [PASS | LOW | NOT SET]

CI/CD Integration:
  Coverage upload         codecov/coveralls          [CONFIGURED | MISSING]
  Artifact upload         coverage reports           [CONFIGURED | MISSING]

Overall: [X issues found]

If --check-only, stop here.

Step 4: Configure coverage (if --fix or user confirms)

Apply coverage configuration based on detected framework. Use templates from REFERENCE.md:

  1. Install coverage provider (e.g., @vitest/coverage-v8, pytest-cov)
  2. Update config file with thresholds, reporters, exclusions
  3. Add scripts to package.json or pyproject.toml
  4. Configure CI/CD with Codecov upload and artifact storage

Step 5: Update standards tracking

Update .project-standards.yaml:

standards_version: "2025.1"
last_configured: "[timestamp]"
components:
  coverage: "2025.1"
  coverage_threshold: 80
  coverage_provider: "[v8|istanbul|pytest-cov|llvm-cov]"
  coverage_reporters: ["text", "json", "html", "lcov"]
  coverage_ci: "codecov"

Step 6: Print final report

Print a summary of changes applied, scripts added, and next steps for verifying coverage.

For detailed configuration templates, see REFERENCE.md.

Agentic Optimizations

ContextCommand
Quick compliance check/configure:coverage --check-only
Auto-fix all issues/configure:coverage --fix
Custom threshold/configure:coverage --fix --threshold 90
Check coverage config existsfind. -maxdepth 1 -name 'vitest.config.*' -o -name 'jest.config.*' 2>/dev/null
Verify coverage directorytest -d coverage && echo "EXISTS"

Flags

FlagDescription
--check-onlyReport status without offering fixes
--fixApply all fixes automatically without prompting
--threshold <percentage>Set coverage threshold (default: 80)

Examples

# Check compliance and offer fixes
/configure:coverage

# Check only, no modifications
/configure:coverage --check-only

# Auto-fix with custom threshold
/configure:coverage --fix --threshold 90

Error Handling

  • No test framework detected: Suggest running /configure:tests first
  • Coverage provider missing: Offer to install
  • Invalid threshold: Reject values <0 or >100
  • CI token missing: Warn about Codecov/Coveralls setup

See Also

适合场景

01

研究助手

02

事实核查

03

知识库问答

04

带来源的搜索总结

能力概览

能力 1

组合搜索和大模型调用

能力 2

支持多来源检索和总结

能力 3

强调引用来源和事实核查

能力 4

适合研究型 Agent 流程

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

37.88%
按下载量换算159

Claude

28.21%
按下载量换算118

Cursor

18.02%
按下载量换算76

Gemini CLI

10.15%
按下载量换算43

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

执行命令

安装流程涉及命令执行,可能通过 npx skills add https://github.com/laurigates/claude-plugins --skill configure-coverage 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills