Coverage Analysis
Cratis rules in .cratis/ai/rules/ (including csharp.md, specs.csharp.md, and orleans.md) and the cratis-* skills win where they differ. The C# and Python pairing scripts differ on .Spec/.Specs project suffixes; Cratis specification projects end in .Specs. Coverage is not behavior evidence.
Purpose
Explain what .NET coverage evidence proves, reconcile target arithmetic, and
identify the code blocking progress. Add complexity/CRAP ranking only when the
user explicitly asks for risk hotspots, CRAP, priorities by risk, or refactoring
safety.
When to Use
Use this skill for interpreting supplied .NET line/branch/condition evidence,
coverage gaps and plateaus, target arithmetic, or explicit project-wide
coverage-backed risk analysis.
When Not to Use
- Named method, class, or file CRAP/refactoring-safety analysis — out of scope; analyze that target directly
- Static source-to-test pairing or listing files with no tests — out of scope
- Behavioral or pseudo-mutation gaps in existing tests — out of scope
- Test trait/category distributions or coverage shape by test type — out of scope
- Writing or generating tests — this skill identifies where tests are needed, not write them
- General test execution unrelated to coverage or CRAP analysis
- Only collecting .NET coverage or printing a raw percentage with no diagnosis — use
run-tests; use native tooling for non-.NET coverage collection or analysis. Interpreting .NET line/branch gaps remains in scope here
Inputs
| Input |
Required |
Default |
Description |
| Project/solution path |
No |
Current directory |
Path to the .NET solution or project |
| Line coverage threshold |
No |
80% |
Minimum acceptable line coverage |
| Branch coverage threshold |
No |
70% |
Minimum acceptable branch coverage |
| Existing Cobertura path |
No |
Discover only if not supplied |
Preferred input; never rerun tests when usable |
| CRAP threshold |
No |
30 |
Used only for explicit risk/CRAP requests |
| Hotspot count |
No |
3 |
Explicit risk requests only; cap at 10 unless the user asks for more |
Discover optional inputs from the workspace. Do not ask for a project path when
the current directory or a supplied report is sufficient.
Choose the smallest matching path
| User intent |
Required work |
Do not do |
| Explain a supplied excerpt, condition, or summary |
Answer directly from the supplied evidence |
Tools, CRAP, discovery, report files |
| Interpret a supplied Cobertura path or diagnose a plateau |
Read that report, reconcile totals, name all material gaps, answer directly |
Rerun tests, install tools, compute CRAP, or generate files unless explicitly requested |
| Rank risk hotspots, compute project-wide CRAP, or assess refactoring safety |
Use the supplied/existing report, read references/guidelines.md, and compute CRAP before ranking |
Coverage-only ranking or a full report template unless requested |
| Analyze coverage when no report exists |
Invoke run-tests to collect coverage with the repository-compatible runner, then analyze the generated report |
Choose or execute a test command independently; CRAP unless risk was requested |
| Produce a full markdown/HTML/CSV report |
First deliver the direct answer; then read references/output-format.md or references/report-generation.md |
Report generation before the answer |
Words such as analyze coverage, what is blocking coverage, or why is
coverage stuck do not by themselves request CRAP. Explicit signals include
risk hotspot, CRAP, complexity-weighted priority, safe to refactor,
or an equivalent request to combine complexity with coverage.
Existing-data fast path
When the user supplies a coverage excerpt, summary, or valid Cobertura path:
- Treat it as authoritative input and start there.
- Do not discover the solution or test projects unless source mapping is necessary.
- Do not run
dotnet test, install ReportGenerator, add a coverage package, or
read references/setup-discovery.md or references/report-generation.md.
- Do not write
coverage-analysis.md or create a report directory unless the user
requested a saved/full report.
- For interpretation and plateau questions, parse only the evidence needed to
answer. For explicit project-wide risk requests, use the bundled scripts as
described in
references/guidelines.md.
A failed read/view operation is not proof that a named path does not exist.
Classify the failure, then make one targeted existence probe and use a normalized
path or alternate reader only for confirmed tool availability, transport, or
path-normalization failures and only after verifying the canonical path remains
inside the workspace. Stop on content-exclusion, permission/policy,
workspace-boundary, or unknown failures. Report a missing path only when the
independent probe also fails; do not broaden the search or substitute another
artifact.
Collection path
Use this path only when no usable coverage evidence exists and the user asked for
analysis that requires it.
- Read
references/setup-discovery.md.
- Prefer existing Cobertura discovered under the requested root.
- If none exists, invoke
run-tests for repository overlay, platform, runner,
and command selection, and have it collect Cobertura once per entry point.
- Analyze the resulting Cobertura. Compute CRAP only if risk analysis was
explicitly requested.
When the workspace contains the project/test manifests needed by this path,
perform discovery directly and delegate collection to run-tests. Do not ask
the user to attach files or pre-run coverage that the current workspace lets
you inspect and generate.
Do not modify production code. Any incidental test-project change needed for
collection is owned by run-tests; include that change and its revert command
in the final analysis.
The automatic collection path is for SDK-style projects. For classic non-SDK or
packages.config projects, use only a repository-owned coverage command. If none
exists, stop and request Cobertura XML. Never migrate the project, inject an
SDK-style provider, create a wrapper project, or report substitute coverage from
another assembly.
Interpretation and arithmetic invariants
- A line hit proves execution, not both decision outcomes.
condition-coverage="50% (1/2)" proves one reported outcome ran, but not which
one. Recommend forcing the opposite outcome. Without source, never invent likely
predicates or claim whether true or false is missing. State that compound
predicates need independently exercised operands and short-circuit combinations
when applicable; do not infer the exact combinations without source or fuller XML.
- Derive overall totals from Cobertura's covered/valid line counts. For target
T, required covered lines are ceiling(valid lines × T).
- Projected coverage is
(current covered lines + newly covered distinct lines) / valid lines. State assumptions such as fully covering a method.
- When asked whether one member can reach a target, show its maximum projected
total and at least one concrete sufficient combination of supplied members or
line gains. If no supplied combination is sufficient, say so.
- For a multi-member target, name the exact combination and resulting covered /
valid total; saying only "combine it with another member" is incomplete.
- Reconcile member gaps against project totals. Method line ranges can overlap or
omit class-level lines, so do not sum method counts as project truth.
- Never call one member the sole, entire, or all remaining gap unless
its distinct uncovered lines exactly reconcile with the project total and no
other below-threshold member remains.
- Name every supplied or extracted below-threshold member, but keep detail
proportional: lead with the blockers, summarize the remainder in one sentence
or a compact table.
Response contract
Answer the user's question in the first 2–4 sentences.
- Excerpt or arithmetic question: one explanation plus the next test or member
priority. No dashboard.
- Existing-report interpretation or plateau: overall line/branch coverage,
blocking members, reconciled target impact, and 1–3 recommendations. Use at
most one compact table.
- Explicit risk/CRAP request: top 3 actual hotspots by default, supporting
complexity/coverage/CRAP values, remaining flagged count, and 1–3 priorities.
Exclude fully covered low-risk methods from the hotspot table. Never exceed 10
rows unless the user requests a larger count. For refactoring safety, rank risky
methods by CRAP rather than raw coverage alone, then name comparatively safe
well-covered methods separately.
- Explicit full report request: read
references/output-format.md. Save the
report only then.
Report only artifacts that exist. Do not announce inaccessible output paths or
failed optional file writes when no file was requested.
Optional reports
HTML/CSV/markdown files are not part of normal analysis. Generate them only when
the user explicitly requests report files or a CI artifact.
- Deliver the direct coverage/risk answer first.
- For a full markdown report, read
references/output-format.md and save it.
- For HTML/CSV, then read
references/report-generation.md. Do not install
ReportGenerator before the direct answer, and do not retry a failed install.
Validation
- Confirm a supplied report was used without test execution or tool installation.
- Reconcile covered, valid, and uncovered line totals before projecting impact.
- Confirm every stated blocker comes from supplied or extracted evidence.
- If CRAP was requested, spot-check one score using
references/guidelines.md.
- If files were requested, verify they exist before reporting their paths.
Common Pitfalls
- Existing report triggers setup work — stop. Analyze the named artifact first.
- Generic analysis triggers CRAP — stop. CRAP requires explicit risk intent.
- One method is called the entire gap — reconcile distinct uncovered lines and
the full below-threshold set first.
- A small request gets a dashboard — scale down to a direct answer or one table.
- No Cobertura from collection — report the collection failure; do not invent
substitute coverage.
- Compiler-generated method names — verify suspicious async, lambda, or local
function names against source before presenting them as user-authored members.
- Test exit code 1 — coverage may still exist; proceed with a warning. Other
nonzero build failures stop the collection path.
Reference navigation
- Read scripts/Compute-CrapScores.ps1 when working on Compute CrapScores.
- Read scripts/CoverageData.ps1 when working on CoverageData.
- Read scripts/Extract-MethodCoverage.ps1 when working on Extract MethodCoverage.
1---2name: coverage-analysis3description: Use when interpreting supplied .NET coverage evidence or an explicit coverage-collection request. Not for hypothetical change-survival questions, CRAP for one target, writing tests or running tests without a coverage request.4license: MIT5metadata:6 source: https://skillmd.com/skills/cratis/coverage-analysis7---89<!-- Modified by Cratis from dotnet's original (MIT): frontmatter, applicability, navigation and the changes listed in NOTICE. Upstream: https://github.com/dotnet/skills (plugins/dotnet-test/skills/coverage-analysis/SKILL.md; see NOTICE) -->1011# Coverage Analysis1213Cratis rules in `.cratis/ai/rules/` (including `csharp.md`, `specs.csharp.md`, and `orleans.md`) and the `cratis-*` skills win where they differ. The C# and Python pairing scripts differ on `.Spec`/`.Specs` project suffixes; Cratis specification projects end in `.Specs`. Coverage is not behavior evidence.1415## Purpose1617Explain what .NET coverage evidence proves, reconcile target arithmetic, and18identify the code blocking progress. Add complexity/CRAP ranking only when the19user explicitly asks for risk hotspots, CRAP, priorities by risk, or refactoring20safety.2122## When to Use2324Use this skill for interpreting supplied .NET line/branch/condition evidence,25coverage gaps and plateaus, target arithmetic, or explicit project-wide26coverage-backed risk analysis.2728## When Not to Use2930- **Named method, class, or file CRAP/refactoring-safety analysis** — out of scope; analyze that target directly31- **Static source-to-test pairing or listing files with no tests** — out of scope32- **Behavioral or pseudo-mutation gaps in existing tests** — out of scope33- **Test trait/category distributions or coverage shape by test type** — out of scope34- **Writing or generating tests** — this skill identifies where tests are needed, not write them35- **General test execution** unrelated to coverage or CRAP analysis36- **Only collecting .NET coverage or printing a raw percentage with no diagnosis** — use `run-tests`; use native tooling for non-.NET coverage collection or analysis. Interpreting .NET line/branch gaps remains in scope here3738## Inputs3940| Input | Required | Default | Description |41|-------|----------|---------|-------------|42| Project/solution path | No | Current directory | Path to the .NET solution or project |43| Line coverage threshold | No | 80% | Minimum acceptable line coverage |44| Branch coverage threshold | No | 70% | Minimum acceptable branch coverage |45| Existing Cobertura path | No | Discover only if not supplied | Preferred input; never rerun tests when usable |46| CRAP threshold | No | 30 | Used only for explicit risk/CRAP requests |47| Hotspot count | No | 3 | Explicit risk requests only; cap at 10 unless the user asks for more |4849Discover optional inputs from the workspace. Do not ask for a project path when50the current directory or a supplied report is sufficient.5152## Choose the smallest matching path5354| User intent | Required work | Do not do |55|-------------|---------------|-----------|56| Explain a supplied excerpt, condition, or summary | Answer directly from the supplied evidence | Tools, CRAP, discovery, report files |57| Interpret a supplied Cobertura path or diagnose a plateau | Read that report, reconcile totals, name all material gaps, answer directly | Rerun tests, install tools, compute CRAP, or generate files unless explicitly requested |58| Rank risk hotspots, compute project-wide CRAP, or assess refactoring safety | Use the supplied/existing report, read `references/guidelines.md`, and compute CRAP before ranking | Coverage-only ranking or a full report template unless requested |59| Analyze coverage when no report exists | Invoke `run-tests` to collect coverage with the repository-compatible runner, then analyze the generated report | Choose or execute a test command independently; CRAP unless risk was requested |60| Produce a full markdown/HTML/CSV report | First deliver the direct answer; then read `references/output-format.md` or `references/report-generation.md` | Report generation before the answer |6162Words such as **analyze coverage**, **what is blocking coverage**, or **why is63coverage stuck** do not by themselves request CRAP. Explicit signals include64**risk hotspot**, **CRAP**, **complexity-weighted priority**, **safe to refactor**,65or an equivalent request to combine complexity with coverage.6667## Existing-data fast path6869When the user supplies a coverage excerpt, summary, or valid Cobertura path:7071- Treat it as authoritative input and start there.72- Do not discover the solution or test projects unless source mapping is necessary.73- Do not run `dotnet test`, install ReportGenerator, add a coverage package, or74 read `references/setup-discovery.md` or `references/report-generation.md`.75- Do not write `coverage-analysis.md` or create a report directory unless the user76 requested a saved/full report.77- For interpretation and plateau questions, parse only the evidence needed to78 answer. For explicit project-wide risk requests, use the bundled scripts as79 described in `references/guidelines.md`.8081A failed read/view operation is not proof that a named path does not exist.82Classify the failure, then make one targeted existence probe and use a normalized83path or alternate reader only for confirmed tool availability, transport, or84path-normalization failures and only after verifying the canonical path remains85inside the workspace. Stop on content-exclusion, permission/policy,86workspace-boundary, or unknown failures. Report a missing path only when the87independent probe also fails; do not broaden the search or substitute another88artifact.8990## Collection path9192Use this path only when no usable coverage evidence exists and the user asked for93analysis that requires it.94951. Read `references/setup-discovery.md`.962. Prefer existing Cobertura discovered under the requested root.973. If none exists, invoke `run-tests` for repository overlay, platform, runner,98 and command selection, and have it collect Cobertura once per entry point.994. Analyze the resulting Cobertura. Compute CRAP only if risk analysis was100 explicitly requested.101102When the workspace contains the project/test manifests needed by this path,103perform discovery directly and delegate collection to `run-tests`. Do not ask104the user to attach files or pre-run coverage that the current workspace lets105you inspect and generate.106107Do not modify production code. Any incidental test-project change needed for108collection is owned by `run-tests`; include that change and its revert command109in the final analysis.110111The automatic collection path is for SDK-style projects. For classic non-SDK or112`packages.config` projects, use only a repository-owned coverage command. If none113exists, stop and request Cobertura XML. Never migrate the project, inject an114SDK-style provider, create a wrapper project, or report substitute coverage from115another assembly.116117## Interpretation and arithmetic invariants118119- A line hit proves execution, not both decision outcomes.120- `condition-coverage="50% (1/2)"` proves one reported outcome ran, but not which121 one. Recommend forcing the opposite outcome. Without source, never invent likely122 predicates or claim whether true or false is missing. State that compound123 predicates need independently exercised operands and short-circuit combinations124 when applicable; do not infer the exact combinations without source or fuller XML.125- Derive overall totals from Cobertura's covered/valid line counts. For target126 `T`, required covered lines are `ceiling(valid lines × T)`.127- Projected coverage is `(current covered lines + newly covered distinct lines) /128 valid lines`. State assumptions such as fully covering a method.129- When asked whether one member can reach a target, show its maximum projected130 total and at least one concrete sufficient combination of supplied members or131 line gains. If no supplied combination is sufficient, say so.132- For a multi-member target, name the exact combination and resulting covered /133 valid total; saying only "combine it with another member" is incomplete.134- Reconcile member gaps against project totals. Method line ranges can overlap or135 omit class-level lines, so do not sum method counts as project truth.136- Never call one member the **sole**, **entire**, or **all** remaining gap unless137 its distinct uncovered lines exactly reconcile with the project total and no138 other below-threshold member remains.139- Name every supplied or extracted below-threshold member, but keep detail140 proportional: lead with the blockers, summarize the remainder in one sentence141 or a compact table.142143## Response contract144145Answer the user's question in the first 2–4 sentences.146147- **Excerpt or arithmetic question:** one explanation plus the next test or member148 priority. No dashboard.149- **Existing-report interpretation or plateau:** overall line/branch coverage,150 blocking members, reconciled target impact, and 1–3 recommendations. Use at151 most one compact table.152- **Explicit risk/CRAP request:** top 3 actual hotspots by default, supporting153 complexity/coverage/CRAP values, remaining flagged count, and 1–3 priorities.154 Exclude fully covered low-risk methods from the hotspot table. Never exceed 10155 rows unless the user requests a larger count. For refactoring safety, rank risky156 methods by CRAP rather than raw coverage alone, then name comparatively safe157 well-covered methods separately.158- **Explicit full report request:** read `references/output-format.md`. Save the159 report only then.160161Report only artifacts that exist. Do not announce inaccessible output paths or162failed optional file writes when no file was requested.163164## Optional reports165166HTML/CSV/markdown files are not part of normal analysis. Generate them only when167the user explicitly requests report files or a CI artifact.1681691. Deliver the direct coverage/risk answer first.1702. For a full markdown report, read `references/output-format.md` and save it.1713. For HTML/CSV, then read `references/report-generation.md`. Do not install172 ReportGenerator before the direct answer, and do not retry a failed install.173174## Validation175176- Confirm a supplied report was used without test execution or tool installation.177- Reconcile covered, valid, and uncovered line totals before projecting impact.178- Confirm every stated blocker comes from supplied or extracted evidence.179- If CRAP was requested, spot-check one score using `references/guidelines.md`.180- If files were requested, verify they exist before reporting their paths.181182## Common Pitfalls183184- **Existing report triggers setup work** — stop. Analyze the named artifact first.185- **Generic analysis triggers CRAP** — stop. CRAP requires explicit risk intent.186- **One method is called the entire gap** — reconcile distinct uncovered lines and187 the full below-threshold set first.188- **A small request gets a dashboard** — scale down to a direct answer or one table.189- **No Cobertura from collection** — report the collection failure; do not invent190 substitute coverage.191- **Compiler-generated method names** — verify suspicious async, lambda, or local192 function names against source before presenting them as user-authored members.193- **Test exit code 1** — coverage may still exist; proceed with a warning. Other194 nonzero build failures stop the collection path.195196## Reference navigation197198- Read scripts/Compute-CrapScores.ps1 when working on Compute CrapScores.199- Read scripts/CoverageData.ps1 when working on CoverageData.200- Read scripts/Extract-MethodCoverage.ps1 when working on Extract MethodCoverage.