nikiforovall/coverage-report
plugins/handbook-dotnet/skills/coverage-report/SKILL.md
Generate a .NET code coverage report scoped to files changed in the current branch. Runs tests with coverage collection and produces filtered HTML reports.
$ install --global
skillsauthnpx skillsauth add nikiforovall/claude-code-rules coverage-reportInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 7, 2026, 8:19 PM5.4s1 file scanned
SKILL.md
- name:
- coverage-report
- description:
- Generate a .NET code coverage report scoped to files changed in the current branch. Runs tests with coverage collection and produces filtered HTML reports.
- allowed-tools:
- Bash(dotnet test:*), Bash(dotnet reportgenerator:*), Bash(git diff:*), Bash(git merge-base:*), Bash(start:*), Read, Grep, Glob
Code Coverage Report
Generate a code coverage report scoped to source files changed in the current branch compared to a base branch.
Workflow
1. Determine base branch
Detect the base branch to diff against. Use the MR/PR target branch if known, otherwise default to main or master (whichever exists). Ask the user if ambiguous.
git merge-base --fork-point main HEAD || git merge-base --fork-point master HEAD
2. Detect changed source files
git diff <base-branch> --name-only -- '*.cs'
Filter out test files (paths containing Test, Tests, .Tests, .Test).
If no source files changed, stop and inform the user.
3. Identify test project(s)
Determine which test project(s) to run. Strategies (in order):
- User-specified: If the user names a test project, use it
- Convention-based: Look for test projects whose name matches the changed project (e.g.,
MyProject->MyProject.Tests) - Solution-wide: Run all tests in the solution if scope is unclear
- Ask: If ambiguous, ask the user which test project(s) to run
4. Clean previous results
rm -rf TestResults/
5. Run tests with coverage
dotnet test <test-project-or-solution> \
--collect:"XPlat Code Coverage" \
--results-directory ./TestResults/
6. Build file filters
From the changed file list (step 2), extract basenames and build a filter string:
+*FileName1.cs;+*FileName2.cs;+*FileName3.cs
7. Generate report
dotnet reportgenerator \
-reports:"TestResults/**/coverage.cobertura.xml" \
-targetdir:"TestResults/CoverageReport" \
-reporttypes:"Html;TextSummary" \
-filefilters:"<filters>"
8. Display results
- Print
TestResults/CoverageReport/Summary.txtto the terminal - Open the HTML report (platform-aware):
- Windows:
start TestResults/CoverageReport/index.html - macOS:
open TestResults/CoverageReport/index.html - Linux:
xdg-open TestResults/CoverageReport/index.html
- Windows:
Tips
- For large solutions, scope to specific test projects to speed up collection
- The
-filefiltersflag accepts wildcards -- basename matching avoids path sensitivity
Related Skills
nikiforovall/visual-explainer
development
VerifiedTrustedCommunity
Generate beautiful, self-contained HTML pages that visually explain systems, code changes, plans, and data. Use when the user asks for a diagram, architecture overview, diff review, plan review, project recap, comparison table, or any visual explanation of technical concepts. Also use proactively when you are about to render a complex ASCII table (4+ rows or 3+ columns) — present it as a styled HTML page instead.
123SKILL.mdUpdated May 16, 2026
nikiforovall/glab
tools
VerifiedTrustedCommunity
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.
123SKILL.mdUpdated May 16, 2026
nikiforovall/plugins/handbook-reflect/skills/reflect
tools
VerifiedTrustedCommunity
--- name: reflect description: Analyze a Claude Code session for "wrong-turn" moments (corrections, retries, waste, reversals, dead-ends) and produce an interactive HTML dashboard with copy-able recommendations (CLAUDE.md rules, docs, scripts, hooks, memory entries, sub-skills, etc.) that would help future agents reach the goal faster. Defaults to reflecting on the current in-context session; optionally accepts a session ID or JSONL path. Use when the user invokes /reflect or asks to learn from
119SKILL.mdUpdated Apr 26, 2026
nikiforovall/plugins/handbook-reflect/skills/reflect-tree
tools
VerifiedTrustedCommunity
--- name: reflect-tree description: Visualize a Claude Code session as a quest/skill tree — a navigable SVG graph where nodes are turns and edges show flow, with distinct visual encoding for normal flow, dead-ends, corrections, retries, reversals, and backtracking. Sibling to /reflect (which produces an incidents+recommendations dashboard); this one shows the journey itself. Defaults to the current in-context session; optionally accepts a session ID or JSONL path. Use when the user invokes /refl
119SKILL.mdUpdated Apr 26, 2026