amplicode/spring-skills

coverage

Measure a project's code coverage and report the coverage number.

Ver código-fonte

Como usar

  1. Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
  2. Consulte no original as ferramentas, credenciais e ambientes necessários.
  3. Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/amplicode/spring-skills --skill coverage

Antes de começar

  • A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
  • Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

Coverage

What to cover

Same two dimensions as the run-tests skill — test type, optionally narrowed to a module / group:

Coverage byTypical Gradle taskMeaning
all (default)jacocoTestReportBoth suites merged (test + testIntgr) — what the baseline is expressed in. Needs Docker.
unitjacocoTestReport -x testIntgrWhat the fast tests alone cover.
integrationjacocoTestReport -x testWhat 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.

Relacionados por tarefa

do mesmo repositório

Mais Skills

Todos os Skills
amplicode
Comunidade

java-debug

Safety rules, workflows, and tool reference for debugging applications via IntelliJ debugger: breakpoints, debug sessions, stepping, evaluating expressions, inspecting runtime state. TRIGGER when: user wants to debug, investigate a bug, set breakpoints, inspect runtime behavior, step through code, or understand why code behaves unexpectedly at runtime. Trigger phrases (EN): "debug", "breakpoint", "step through", "step into", "step over", "why does this crash", "why is this null", "launch in debu

instalações
2
GitHub Stars
131
Atualizado
6 de set.
amplicode
Comunidade

spring-data-jdbc

Rules and guidelines for working with Spring Data JDBC in the project. ALWAYS use this skill when adding, removing, or modifying Spring Data JDBC entities (@Table from org.springframework.data.relational.core.mapping), aggregates, AggregateReference links, embedded objects, @MappedCollection associations, or Spring Data JDBC repositories (CrudRepository / ListCrudRepository). Trigger on any request that touches @Table, @Column, @MappedCollection, @Embedded annotations from spring-data-relational

instalações
1
GitHub Stars
128
Atualizado
6 de set.
amplicode
Comunidade

spring-data-jpa

Rules and guidelines for working with Spring Data JPA in the project. ALWAYS use this skill when adding, removing, or modifying JPA entities, repositories, or projections. Trigger on any request that involves changing entity structure, adding new entities, modifying field annotations, updating database mappings, creating or modifying Spring Data repositories, or defining query projections (interfaces, DTOs).

instalações
1
GitHub Stars
128
Atualizado
6 de set.