Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Test Coverage

ASecurity

Run .NET Coverlet coverage, report Sonar-aligned metrics, and evaluate against a threshold (default 80%). Use for coverage reports or when invoking /test-coverage.

6 stars
0 votes
0 copies
0 views
Added 9/25/2026
ai-agentsshellbashrailscode-reviewgitapi

Works with

api

Security Analysis

A100/100

Pro scans all 11 files and shows the line behind each finding

Scanned 9/26/2026

$npx -y skills add tibursocampos/agent-dev-toolkit --skill test-coverage --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Test Coverage?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Test Coverage
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tibursocampos-test-coverage/badge)](https://www.skillsdirectory.com/skills/tibursocampos-test-coverage)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: test-coverage
description: Run .NET Coverlet coverage, report Sonar-aligned metrics, and evaluate against a threshold (default 80%). Use for coverage reports or when invoking /test-coverage.
---

## STOP - Read before ANY tool call

1. Read `{{GUARDRAILS_PATH}}`
2. Read `_shared/sdd-artifacts/SESSION.md`; load session-state for `$Cwd`
3. If the relevant gate is not approved: **STOP** - ask user **(pt-BR)** - do **NOT** Write/Shell
4. SDD/develop skills: after **ONE** step/task, **STOP** session - handoff only
5. This skill body is **English**; user-facing prompts may be **(pt-BR)**

### Step -1 - Gate check (report in chat before continuing)

```
Gate check:
[ ] guardrails.mdc read
[ ] SESSION.md read; session-state loaded
[ ] PIPELINE.md read (SDD skills only)
[ ] User confirmed current action (sim)
-> If any unchecked: STOP
```

---

## Trigger

Invoke when the user asks for: `/test-coverage`, `coverage report`, `coverage`, or when a PLAN step / `code-review` requires coverage evidence.

**Arguments (optional):**

| Input | Meaning |
|-------|---------|
| Base branch | `main`, `develop` - ask once if missing (same as `code-review`) |
| Test project path | `path/to/Tests.csproj` - auto-detect `*Tests.csproj` / `*.Tests.csproj` if omitted |
| Threshold | Minimum line coverage on **changed production `.cs` files** (default: **80**) |
| Target | **100** - aspirational; document gaps when below 100 but >= threshold |

## Outcome

A structured **coverage report** in **pt-BR** with:

- **Coverage on new code** - line coverage on changed production files vs base branch
- **Overall branch coverage** - solution-wide line coverage after tests
- **Per-file breakdown** - each changed production file with line %
- **Decision:** Pass (>= threshold) or Fail (< threshold) with gap list

Does not modify code unless the user asks for test additions in a follow-up.

## Lazy-load

| When | Path |
|------|------|
| Reference index (routing only) | `{{TOOLKIT_ROOT}}/skills/test-coverage/reference.md` |
| Process step detail (lazy) | `{{TOOLKIT_ROOT}}/skills/test-coverage/references/<section>.md` |
| Host session mode (Agent for shell) | `{{TOOLKIT_ROOT}}/skills/_shared/sdd-artifacts/PIPELINE.md` section Host session mode |
| Caveman Mode (if active) | `{{TOOLKIT_ROOT}}/skills/_shared/caveman/CAVEMAN.md` - **Full cap** |
| Add tests for gaps | `{{TOOLKIT_ROOT}}/skills/_shared/dotnet-guidelines/csharp-patterns.md` |
| Commit | `/commit` |

**Never by default:** do not preload all `references/*.md` or full guideline packs. Load **one** section file per Process step — never full `reference.md` when a section exists (`SKILL-REFERENCE-RETRIEVAL.md`).

## Reference routing

| Situation | Path |
|-----------|------|
| Prerequisites | `references/prerequisites.md` |
| Exclusions | `references/exclusions.md` |
| Commands | `references/commands.md` |
| Metrics | `references/metrics.md` |
| On-disk artifacts | `references/artifacts.md` |
| Report template | `references/report-template.md` |
| Scoped discovery | `references/scoped-discovery.md` |
| Integrations | `references/integrations.md` |
| Troubleshooting | `references/troubleshooting.md` |
## Process

Read `references/<section>.md` for commands, metrics, and templates — **not** full `reference.md`.

### Step -1b - Caveman Mode (Full cap)
1. Read `{{SDD_ROOT}}/preferences.json` (create `{ "caveman_mode": false, "caveman_level": "full" }` if missing).
2. If `caveman_mode` is false: continue without compression.
3. If true: load `{{TOOLKIT_ROOT}}/skills/_shared/caveman/CAVEMAN.md`; apply **Full** participation cap + prefs `caveman_level` (Lite skills never escalate); show once: `[Caveman] Modo ativo (respostas compactas, level={effective}). Digite caveman off para desativar.`
4. Honor `caveman on|off|status|lite|full|ultra` (and `stop caveman` / `normal mode`) during the session.
5. Auto-Clarity + never-compress gates/drafts/paths per `CAVEMAN.md`.

### -1. Mode
`PIPELINE.md`: **Agent** required for `dotnet test` and ReportGenerator. In Plan/Ask, explain limitation and list expected paths under `TestResults/` after the user switches to Agent.

### 0. Workspace
Confirm **target .NET repository** (`.sln` or `*Tests.csproj`). If the workspace is `agent-dev-toolkit` only (no test projects), stop and ask which consumer repo to open. Detect stack; read `AGENTS.md` / `README.md` when present.

### 1. Resolve scope
**Base branch:** user argument, or `main` / `develop` (ask once if ambiguous).

```bash
git fetch origin   # when remote comparison is needed
git rev-parse --abbrev-ref HEAD
git diff <base>...HEAD --name-only -- "*.cs"
```

Filter to **production** changed files per `references/exclusions.md`. Record the list for per-file metrics. Large repos: see `references/scoped-discovery.md`.

### 2. Prerequisites check
Before running tests, verify per `references/prerequisites.md`. If `coverlet.collector` is missing, stop with install instructions - do not fail silently.

### 3. Collect coverage (mandatory ReportGenerator)
1. Run `dotnet test` with Coverlet -> `TestResults/**/coverage.cobertura.xml` per `references/commands.md`.
2. **Always** run ReportGenerator -> `TestResults/CoverageReport/` (`Summary.txt`, `index.html`, Cobertura). Do not finish with XML only.
Use scoped test project when the repo is large or user provided a path.

### 4. Compute metrics
Parse Cobertura / ReportGenerator output per `references/metrics.md` (new code / overall branch / per-file). Exclude migrations, generated code, and test projects from **new code** denominator (`references/exclusions.md`).

### 5. Evaluate threshold
| Result | When |
|--------|------|
| **Pass** | New code coverage >= threshold (default 80%) |
| **Fail** | New code coverage < threshold |
Always note distance to **target 100%** for files below 100% even when Pass.

### 6. Report (chat + on-disk artifacts)
Use `references/report-template.md`. Cite paths from `references/artifacts.md`. **Required in chat:** Summary.txt / index.html / cobertura paths, Resumo table, commands, limitations, approval block (Pass) or gaps (Fail). Do not claim Pass if ReportGenerator output or Cobertura files are missing. Integrations: `references/integrations.md`. Troubleshooting: `references/troubleshooting.md`.

### 7. Handoff
| Situation | Next |
|-----------|------|
| Pass | `/code-review` - paste approval block from report |
| Fail - add tests | `/dotnet-developer` or `/sdd-develop` |
| Build/test broken | `/repair-dotnet-build` |
| Commit coverage tooling in consumer repo | `/commit` |
| SDD feature with PLAN | Last PLAN step or `code-review` after all `sdd-develop` steps |
| Small fix | `/dotnet-developer` to raise coverage, then re-run this skill |
## Must not

- Require SonarLint, Visual Studio, SonarQube login, or corporate pipeline APIs
- Auto-commit, auto-push, or add tests without user request
- Claim Pass when tests did not run, coverlet output is missing, or ReportGenerator was skipped
- Deliver coverage **only** in chat without citing on-disk paths under `TestResults/`
- Count EF migrations, `*.g.cs`, or `*.Designer.cs` in new-code denominator
- Block merge by itself - gate is informational unless PRD/PLAN/`code-review` applies threshold

Attribution

tibursocampostibursocampos
View sourceSee grades on GitHubMore from tibursocampos →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →