사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/amplicode/spring-skills --skill coverage시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
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.
