Skip to content
Skills Library
Programming · Analysis

codecov-coverage

/codecov-coverage

Fetch and analyze code coverage from Codecov API for the linkml project. Use when checking coverage before making a PR, analyzing coverage changes, or finding low-coverage files.

Repository
linkml ↗
Licence
Apache-2.0
Last repository change
27.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
3
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Fetch and analyze code coverage from Codecov API for the linkml project. Use when checking coverage before making a PR, analyzing coverage changes, or finding low-coverage files.

Original author description

Fetch and analyze code coverage from Codecov API for the linkml project. Use when checking coverage before making a PR, analyzing coverage changes, or finding low-coverage files.

How it works

  1. When to Use This Skill
  2. Coverage Expectations
  3. How to Check Coverage
  4. Why Local Coverage Fails
  5. Known Low-Coverage Areas
Original SKILL.md headings · 54 lines, 209 words
SKILL.md preview
---
name: codecov-coverage
description: Fetch and analyze code coverage from Codecov API for the linkml project. Use when checking coverage before making a PR, analyzing coverage changes, or finding low-coverage files.
allowed-tools: WebFetch, Bash
---

# Codecov Coverage Skill

Fetch and analyze code coverage data from Codecov for the LinkML project.

## When to Use This Skill

- Before creating a PR: check that coverage won't decrease
- When adding new code: identify if new files need tests
- When asked about test coverage or low-coverage areas

## Coverage Expectations

**PRs must not decrease coverage.** The CI will flag coverage decreases.

When adding new code:
- New modules should target >80% coverage
- New public functions need at least one test

## How to Check Coverage

### Quick overall percentage
Use WebFetch on:
```
https://codecov.io/gh/linkml/linkml/branch/main/graph/badge.txt
```
Returns plain text like "80%"

### Detailed totals (lines, hits, misses)
Use WebFetch on:
```
https://api.codecov.io/api/v2/github/linkml/repos/linkml/totals
```
Returns JSON with files count, lines, hits, misses, coverage percentage

### File-level coverage report
Use WebFetch on:
```
https://api.codecov.io/api/v2/github/linkml/repos/linkml/report
```
Returns per-file coverage data - useful for finding low-coverage files

## Why Local Coverage Fails

The UV workspace + src layout breaks local coverage. The `.coveragerc` specifies `source = linkml` but packages live at `packages/linkml/src/linkml/`. Use the Codecov API instead.

## Known Low-Coverage Areas

These areas currently have low coverage and may need tests:
- `generators/rustgen/` - experimental
- `generators/dotgen.py` - ~47%
- `converter/cli.py` - ~53%
- `workspaces/` - minimal coverage

Versions

The database has no other skills named codecov-coverage.

Database snapshot: 13.11.2026 · package version 06a8eaa19127 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100resolve-codecov-feedback
    Explicit-use only — invoke when the user explicitly names this skill, or when an active explicitly invoked workflow calls it. Processes Codecov feedback and adds coverage required by an active workflow.
  • 100code-coverage
    When the user wants to measure, interpret, or improve code coverage — line, branch, function, statement, condition, MC/DC coverage. Use when the user mentions "code coverage," "test coverage," "Istanbul," "c8," "JaCoCo," "coverage.py," "Coverlet," "lcov," "Codecov," "Coveralls,"…
  • 100configure-coverage
    Code coverage: thresholds and reporters for Vitest, Jest, pytest, Rust. Use when setting thresholds, adding Codecov/Coveralls, or wiring lcov/HTML reports.
  • 100analyzing-test-coverage
    Analyze code coverage metrics and identify untested code paths. Use when analyzing untested code or coverage gaps. Trigger with phrases like "analyze coverage", "check test coverage", or "find untested code".
  • 100analyzing-test-coverage
    Analyze code coverage metrics and identify untested code paths. Use when analyzing untested code or coverage gaps. Trigger with phrases like "analyze coverage", "check test coverage", or "find untested code".
  • 100cargo-llvm-cov
    cargo-llvm-cov: Rust code coverage with LLVM instrumentation. Use when measuring coverage, enforcing thresholds, generating reports, or integrating codecov/coveralls.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.