Communitygithub.com

springboot-verification

Bucle de verificación para proyectos Spring Boot: compilación, análisis estático, pruebas con cobertura, escaneos de seguridad y revisión de diferencias antes de lanzamientos o PR.

¿Qué es springboot-verification?

Esta habilidad automatiza un ciclo completo de verificación para proyectos Spring Boot, ejecutándose antes de pull requests, después de cambios importantes o antes de despliegues. Incluye fases de compilación, análisis estático con herramientas como SpotBugs, PMD y Checkstyle, pruebas unitarias y de integración con Testcontainers y MockMvc, escaneos de seguridad para vulnerabilidades de dependencias y secretos, y revisión de diferencias. Es compatible con Maven y Gradle. Proporciona una plantilla de informe estructurado y se puede ejecutar en modo continuo para retroalimentación rápida durante sesiones largas. El objetivo es mantener una puerta estricta que trate las advertencias como defectos en sistemas de producción.

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

Preguntar en tu IA favorita

Abre un nuevo chat con esta habilidad de agente ya precargada.

Documentación

Bucle de Verificación Spring Boot

Ejecutar antes de PRs, después de cambios importantes y antes del despliegue.

Cuándo Activarlo

  • Antes de abrir un pull request para un servicio Spring Boot
  • Después de una refactorización importante o actualizaciones de dependencias
  • Verificación previa al despliegue para staging o producción
  • Ejecutar el pipeline completo: compilación → lint → pruebas → escaneo de seguridad
  • Validar que la cobertura de pruebas cumple los umbrales

Fase 1: Compilación

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

Si la compilación falla, detenerse y corregir.

Fase 2: Análisis Estático

Maven (plugins comunes):

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

Gradle (si está configurado):

./gradlew checkstyleMain pmdMain spotbugsMain

Fase 3: Pruebas + Cobertura

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

Informe:

  • Total de pruebas, aprobadas/falladas
  • % de cobertura (líneas/ramas)

Pruebas Unitarias

Probar la lógica del servicio de forma aislada con dependencias simuladas:

@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);
  }
}

Pruebas de Integración con Testcontainers

Probar contra una base de datos real en lugar 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");
  }
}

Pruebas de API con MockMvc

Probar la capa de controladores con el contexto completo de Spring:

@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: Escaneo de Seguridad

# CVEs de dependencias
mvn org.owasp:dependency-check-maven:check
# o
./gradlew dependencyCheckAnalyze

# Secretos en el código fuente
grep -rn "password\s*=\s*\"" src/ --include="*.java" --include="*.yml" --include="*.properties"
grep -rn "sk-\|api_key\|secret" src/ --include="*.java" --include="*.yml"

# Secretos (historial de git)
git secrets --scan  # si está configurado

Hallazgos Comunes de Seguridad

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

# Buscar mensajes de excepción en crudo en respuestas
grep -rn "e\.getMessage()" src/main/ --include="*.java"

# Buscar comodín CORS
grep -rn "allowedOrigins.*\*" src/main/ --include="*.java"

Fase 5: Lint/Formato (puerta opcional)

mvn spotless:apply   # si se usa el plugin Spotless
./gradlew spotlessApply

Fase 6: Revisión de Diferencias

git diff --stat
git diff

Lista de verificación:

  • No quedan registros de depuración (System.out, log.debug sin guardas)
  • Errores y códigos de estado HTTP significativos
  • Transacciones y validación presentes donde sea necesario
  • Cambios de configuración documentados

Plantilla de Salida

INFORME DE VERIFICACIÓN
=======================
Compilación: [APROBADO/FALLADO]
Estático:    [APROBADO/FALLADO] (spotbugs/pmd/checkstyle)
Pruebas:     [APROBADO/FALLADO] (X/Y aprobadas, Z% cobertura)
Seguridad:   [APROBADO/FALLADO] (Hallazgos CVE: N)
Diff:        [X archivos cambiados]

General:     [LISTO / NO LISTO]

Problemas a corregir:
1. ...
2. ...

Modo Continuo

  • Re-ejecutar fases en cambios significativos o cada 30–60 minutos en sesiones largas
  • Mantener un bucle corto: mvn -T 4 test + spotbugs para retroalimentación rápida

Recuerda: La retroalimentación rápida evita sorpresas tardías. Mantén la puerta estricta: trata las advertencias como defectos en sistemas de producción.

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.

Skills relacionados