How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/amplicode/spring-skills --skill coverageBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
Coverage
What to cover
Same two dimensions as the run-tests skill — test type, optionally narrowed to a module / group:
| Coverage by | Typical Gradle task | Meaning |
|---|---|---|
all (default) | jacocoTestReport | Both suites merged (test + testIntgr) — what the baseline is expressed in. Needs Docker. |
unit | jacocoTestReport -x testIntgr | What the fast tests alone cover. |
integration | jacocoTestReport -x test | What the Testcontainers tests alone cover. Needs Docker. |
| + a module / group | --tests <glob>, or a subproject path (:web:test) | Narrows any of the above to one package/class/subproject. |
Pick the path
Probe FIRST, here, before loading either reference — so you read only the one you need. Call steroid_list_projects (via ToolSearch if the tool schema isn't loaded):
- It returns the repo you're in → IDE path: note that entry's
project_name
and follow references/ide.md (runs the coverage Gradle task inside the IDE in its own Run tab). Its steps start already knowing the project_name — don't re-probe.
- It fails, or the repo isn't listed → console Gradle path: follow
references/gradle.md (runs Gradle in the console) and tell the user you used the console fallback because the IDE wasn't reachable.
Both paths end by collecting the result in a Haiku subagent that returns the references/report.md report and nothing else — keeping the long build/coverage output out of the main context. Act on that report in the main model.
