Communitygithub.com

springboot-verification

Loop de verificação para projetos Spring Boot: compilação, análise estática, testes com cobertura, varreduras de segurança e revisão de diff antes de PR ou release.

O que é springboot-verification?

Esta skill define um pipeline completo de verificação para projetos Spring Boot, destinado a ser executado antes de pull requests, após grandes refatorações, upgrades de dependências ou antes de deploy em staging/produção. Ela organiza a verificação em seis fases: 1) compilação com Maven ou Gradle, 2) análise estática com ferramentas como SpotBugs, PMD e Checkstyle, 3) execução de testes unitários, de integração (com Testcontainers) e de API (com MockMvc) com verificação de cobertura ≥80%, 4) varredura de segurança para CVEs em dependências e segredos no código, 5) lint/format opcional com Spotless, e 6) revisão de diff com checklist. A skill fornece exemplos concretos de código Java para testes e comandos de terminal, um template de relatório de verificação e orientações para modo contínuo. É ideal para desenvolvedores que usam Spring Boot e desejam automatizar a garantia de qualidade antes de consolidar mudanças.

Funciona com~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/affaan-m/everything-claude-code/tree/main/skills/springboot-verification

Perguntar na sua IA favorita

Abre um novo chat com esta habilidade de agente já pré-carregada.

Documentação

Loop de Verificação Spring Boot

Execute antes de PRs, após grandes mudanças e pré-deploy.

Quando Ativar

  • Antes de abrir um pull request para um serviço Spring Boot
  • Após grandes refatorações ou upgrades de dependências
  • Verificação pré-deploy para staging ou produção
  • Executar pipeline completo de compilação → lint → testes → varredura de segurança
  • Validar que a cobertura de testes atende aos limites

Fase 1: Compilação

mvn -T 4 clean verify -DskipTests
# ou
./gradlew clean assemble -x test

Se a compilação falhar, pare e corrija.

Fase 2: Análise Estática

Maven (plugins comuns):

mvn -T 4 spotbugs:check pmd:check checkstyle:check

Gradle (se configurado):

./gradlew checkstyleMain pmdMain spotbugsMain

Fase 3: Testes + Cobertura

mvn -T 4 test
mvn jacoco:report   # verificar 80%+ de cobertura
# ou
./gradlew test jacocoTestReport

Relatório:

  • Total de testes, aprovados/reprovados
  • % de cobertura (linhas/ramos)

Testes Unitários

Testar lógica de serviço isoladamente com dependências mockadas:

@ExtendWith(MockitoExtension.class)
class UserServiceTest {

  @Mock private UserRepository userRepository;
  @InjectMocks private UserService userService;

  @Test
  void createUser_validInput_returnsUser() {
    var dto = new CreateUserDto("Alice", "[email protected]");
    var expected = new User(1L, "Alice", "[email protected]");
    when(userRepository.save(any(User.class))).thenReturn(expected);

    var result = userService.create(dto);

    assertThat(result.name()).isEqualTo("Alice");
    verify(userRepository).save(any(User.class));
  }

  @Test
  void createUser_duplicateEmail_throwsException() {
    var dto = new CreateUserDto("Alice", "[email protected]");
    when(userRepository.existsByEmail(dto.email())).thenReturn(true);

    assertThatThrownBy(() -> userService.create(dto))
        .isInstanceOf(DuplicateEmailException.class);
  }
}

Testes de Integração com Testcontainers

Testar contra um banco de dados real em vez de H2:

@SpringBootTest
@Testcontainers
class UserRepositoryIntegrationTest {

  @Container
  static PostgreSQLContainer<?> postgres = new PostgreSQLContainer<>("postgres:16-alpine")
      .withDatabaseName("testdb");

  @DynamicPropertySource
  static void configureProperties(DynamicPropertyRegistry registry) {
    registry.add("spring.datasource.url", postgres::getJdbcUrl);
    registry.add("spring.datasource.username", postgres::getUsername);
    registry.add("spring.datasource.password", postgres::getPassword);
  }

  @Autowired private UserRepository userRepository;

  @Test
  void findByEmail_existingUser_returnsUser() {
    userRepository.save(new User("Alice", "[email protected]"));

    var found = userRepository.findByEmail("[email protected]");

    assertThat(found).isPresent();
    assertThat(found.get().getName()).isEqualTo("Alice");
  }
}

Testes de API com MockMvc

Testar a camada de controlador com contexto Spring completo:

@WebMvcTest(UserController.class)
class UserControllerTest {

  @Autowired private MockMvc mockMvc;
  @MockBean private UserService userService;

  @Test
  void createUser_validInput_returns201() throws Exception {
    var user = new UserDto(1L, "Alice", "[email protected]");
    when(userService.create(any())).thenReturn(user);

    mockMvc.perform(post("/api/users")
            .contentType(MediaType.APPLICATION_JSON)
            .content("""
                {"name": "Alice", "email": "[email protected]"}
                """))
        .andExpect(status().isCreated())
        .andExpect(jsonPath("$.name").value("Alice"));
  }

  @Test
  void createUser_invalidEmail_returns400() throws Exception {
    mockMvc.perform(post("/api/users")
            .contentType(MediaType.APPLICATION_JSON)
            .content("""
                {"name": "Alice", "email": "not-an-email"}
                """))
        .andExpect(status().isBadRequest());
  }
}

Fase 4: Varredura de Segurança

# CVEs de dependências
mvn org.owasp:dependency-check-maven:check
# ou
./gradlew dependencyCheckAnalyze

# Segredos no código-fonte
grep -rn "password\s*=\s*\"" src/ --include="*.java" --include="*.yml" --include="*.properties"
grep -rn "sk-\|api_key\|secret" src/ --include="*.java" --include="*.yml"

# Segredos (histórico git)
git secrets --scan  # se configurado

Achados Comuns de Segurança

# Verificar System.out.println (usar logger no lugar)
grep -rn "System\.out\.print" src/main/ --include="*.java"

# Verificar mensagens de exceção cruas em respostas
grep -rn "e\.getMessage()" src/main/ --include="*.java"

# Verificar wildcard CORS
grep -rn "allowedOrigins.*\*" src/main/ --include="*.java"

Fase 5: Lint/Formatação (portão opcional)

mvn spotless:apply   # se usando o plugin Spotless
./gradlew spotlessApply

Fase 6: Revisão de Diff

git diff --stat
git diff

Lista de verificação:

  • Nenhum log de debug deixado (System.out, log.debug sem guards)
  • Erros e status HTTP significativos
  • Transações e validação presentes onde necessário
  • Mudanças de configuração documentadas

Template de Saída

RELATÓRIO DE VERIFICAÇÃO
========================
Compilação: [APROVADO/REPROVADO]
Estática:   [APROVADO/REPROVADO] (spotbugs/pmd/checkstyle)
Testes:     [APROVADO/REPROVADO] (X/Y aprovados, Z% cobertura)
Segurança:  [APROVADO/REPROVADO] (achados CVE: N)
Diff:       [X arquivos alterados]

Geral:      [PRONTO / NÃO PRONTO]

Problemas a Corrigir:
1. ...
2. ...

Modo Contínuo

  • Reexecute as fases em mudanças significativas ou a cada 30–60 minutos em sessões longas
  • Mantenha um loop curto: mvn -T 4 test + spotbugs para feedback rápido

Lembrete: Feedback rápido supera surpresas tardias. Mantenha o portão rigoroso—trate avisos como defeitos em sistemas de produção.

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

accessibility

Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA. Use when building or auditing UI that must meet WCAG 2.2 Level AA, or when reviewing a change for keyboard, contrast, or screen-reader support.

affaan-m/claude-api

Anthropic Claude API patterns for Python and TypeScript. Covers Messages API, streaming, tool use, vision, extended thinking, batches, prompt caching, and Claude Agent SDK. Use when building applications with the Claude API or Anthropic SDKs.

affaan-m/everything-claude-code

End-to-end marketing campaign planning and execution. Covers audience research, positioning, campaign angle definition, landing page copy, email sequences, social posts, ad copy, short-form video scripts, and content calendars. Use as the orchestration layer for multi-channel product launches. Use when planning or executing a multi-channel product launch, or producing landing page, email, social, or ad copy.

affaan-m/everything-claude-code

Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.

affaan-m/everything-claude-code-conventions

Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.

affaan-m/frontend-design

Create distinctive, production-grade frontend interfaces with high design quality. Use when the user asks to build web components, pages, or applications and the visual direction matters as much as the code quality.

affaan-m/gget

gget CLI and Python workflow for quick genomic database queries, sequence lookup, BLAST-style searches, enrichment checks, and reproducible bioinformatics evidence logs.

affaan-m/literature-review

Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.

affaan-m/motion-ui

Production-ready UI motion system for React/Next.js. Use when implementing animations, transitions, or motion patterns.

affaan-m/project-guidelines-example

Example project-specific skill template based on a real production application.

affaan-m/pubmed-database

Direct PubMed and NCBI E-utilities search workflows for biomedical literature, MeSH queries, PMID lookup, citation retrieval, and API-backed literature monitoring.

affaan-m/scholar-evaluation

Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.

affaan-m/uspto-database

USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.

agent-architecture-audit

Full-stack diagnostic for agent and LLM applications. Audits the 12-layer agent stack for wrapper regression, memory pollution, tool discipline failures, hidden repair loops, and rendering corruption. Produces severity-ranked findings with code-first fixes. Essential for developers building agent applications, autonomous loops, or any LLM-powered feature. Use when an agent or LLM feature misbehaves and the failing layer is unknown, or before shipping an agent stack.

agent-eval

Head-to-head comparison of coding agents (Claude Code, Aider, Codex, etc.) on custom tasks with pass rate, cost, time, and consistency metrics. Use when choosing between coding agents, or when a change to an agent setup needs measured pass rate, cost, and time rather than an impression.

agent-harness-construction

Design and optimize AI agent action spaces, tool definitions, and observation formatting for higher completion rates. Use when defining or revising an agent

agentic-engineering

Operate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing. Use when planning or executing engineering work that agents will carry out end to end.

agentic-os

Build persistent multi-agent operating systems on Claude Code. Covers kernel architecture, specialist agents, slash commands, file-based memory, scheduled automation, and state management without external databases. Use when building a persistent multi-agent system on Claude Code with its own memory, commands, and scheduling.

agent-introspection-debugging

Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.

agent-payment-x402

Add x402 payment execution to AI agents with per-task budgets, spending controls, and non-custodial wallets. Supports Base through agentwallet-sdk and X Layer through OKX Payments / OKX Agent Payments Protocol. Use when an agent must pay for something itself and needs per-task budgets, spending controls, and a non-custodial wallet.

Habilidades Relacionadas