Desenvolvimento

Use para revisar, melhorar ou refatorar código Java, focando na qualidade do design de tipos. Isso inclui estabelecer hierarquias de tipos claras, aplicar convenções de nomenclatura consistentes, eliminar a obsessão por primitivos, usar parâmetros de tipo genéricos, criar wrappers com segurança de tipo, projetar interfaces fluentes e garantir tipos numéricos com precisão adequada, como BigDecimal para cálculos financeiros.

Use when you need to implement acceptance tests from a Gherkin .feature file for framework-agnostic Java (no Spring Boot, Quarkus, Micronaut) — finding @acceptance scenarios, happy path with RestAssured, Testcontainers for DB/Kafka, WireMock for external REST. Requires .feature file in context. This should trigger for requests such as Review Java code for acceptance tests; Apply best practices for

Use when you need to apply testing strategies for Java code — RIGHT-BICEP to guide test creation, A-TRIP for test quality characteristics, or CORRECT for verifying boundary conditions. This should trigger for requests such as Review Java code for testing strategies; Apply RIGHT-BICEP testing strategies in Java code; Apply A-TRIP testing strategies in Java code; Apply CORRECT boundary condition ver

Responda como 'Programador Yupi', um ex-engenheiro full-stack da Tencent e influenciador de programação e IA. Oferece conselhos sobre aprendizado de programação, carreira, projetos, empreendedorismo e IA, ou quando solicitado a responder em seu estilo.

Use quando precisar adicionar ou avaliar dependências Maven que melhoram a qualidade do código — incluindo anotações de nulidade (JSpecify), análise estática (Error Prone + NullAway), programação funcional (VAVR) ou teste de arquitetura (ArchUnit) — e desejar uma abordagem consultiva e orientada por perguntas que adicione apenas o que você realmente precisa.

Prove and counter-prove a statement using parallel agents to eliminate confirmation bias. Use when someone says "dialectic", "prove/disprove", "stress test this claim", "is this really true", "argue both sides", or when a statement needs objective analysis from opposing viewpoints.

Interactive git diff annotation review. Generates a cleaned-up diff, opens in editor for user annotations, and addresses feedback in a loop. Activates on "git review", "review changes", "review my changes", "annotate changes", "interactive review".

This skill should be used when user appears confused, frustrated, or shows misalignment between expectations and reality. Triggers on phrases like "I don't understand", "this doesn't make sense", "confused", "wait, shouldn't it...", "why is this happening", "I thought X did Y", contradictory statements, or frustration signals. Analyzes the confusion, explains the actual behavior, and determines if

Show commits since the last tag in a formatted table. Use when user asks "what changed since last release", "commits since last tag", "last-tag", "what's new", or wants to see recent unreleased changes.

Comprehensive PR/issue review - analyzes architecture, tests, identifies unrelated changes mixed in, drafts review comment or issue comment. Use when user asks to review a PR, check a PR, look at PR changes, or comment on an issue.

Systematic root cause analysis for errors, bugs, and unexpected behaviors using 5-Why methodology. Use when user reports errors, build failures, test failures, performance issues, integration problems, or any "it's not working" scenarios.

Use when user asks to create a release, cut a release, or publish a version. Auto-detects GitHub vs GitLab vs Gitea, calculates semantic version, generates release notes from PRs/MRs or commits, shows preview for confirmation before publishing.