skills.rest
zuldare
zuldareCOMMUNITY
Explore all skills by this author →
Website𝕏@erJeremiasGitHub

deep-review

Investigates PR fixes for root causes, transaction safety, and test coverage in Spring Boot applications.

Updated Dec 23, 2025
Search Tags:#code review#pull request#root cause analysis#concurrency#java#transactions#spring boot
One-click install
npx skills add https://github.com/zuldare/apuntesIA --skill deep-review-zuldare
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deep-review
Source: https://github.com/zuldare/apuntesIA/tree/main/skills/deep-review
Command: npx skills add https://github.com/zuldare/apuntesIA --skill deep-review-zuldare

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Standard code reviews often approve fixes that silence symptoms without resolving the underlying bug, letting defects resurface in production. This Skill performs an investigation-first review that reconstructs the original problem, traces real execution flow, and verifies whether a fix addresses the root cause. ## Core Features & Use Cases - Root Cause Analysis: Reconstructs the reported problem independently before reading the fix, flagging symptomatic patches like masking null checks or swallowed exceptions. - Transaction & JPA Audits: Verifies @Transactional boundaries, readOnly misuse, nested transactions, lazy loading risks, and N+1 queries in Spring Boot 3.x / Java 17-21 code. - Impact & Concurrency Analysis: Maps all callers of modified methods and checks async, scheduled, and virtual-thread contexts for shared-state and pinning risks. - Test Quality Verdict: Requires a test that fails on the original code and passes on the fix, then produces a structured verdict (APPROVE / REQUEST CHANGES / REJECT). - Use Case: A recurring production bug gets a one-line null check fix. Run this Skill to discover the null originates from a missing transaction boundary upstream, and that the fix would silently corrupt data in a scheduled job caller. ## Quick Start Ask the AI to run a deep review on the current pull request and produce a root cause verdict with transaction and test coverage findings.

Frequently Asked Questions about deep-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a PR that fixes a recurring bug?▼

Reconstruct the original problem from the issue and stacktrace before reading the fix, then trace the actual execution path to the failure point. Verify the change intercepts the cause rather than adding null checks or exception handling that only hide the symptom.

How to check if a fix addresses root cause or symptom?▼

Compare the fix location against the failure point in the execution flow. Red flags include null checks where nulls should never occur, caught exceptions that should not be thrown, and conditions that bypass the problematic path instead of correcting it.

Why does @Transactional readOnly cause silent data loss in Spring Boot?▼

When a class is annotated with @Transactional(readOnly = true) and a write method does not override it, the save operation runs in a read-only transaction and writes are silently ignored. Always verify write methods declare their own @Transactional without readOnly.

Does this review approach work with Java 21 virtual threads?▼

Yes, it explicitly checks virtual thread risks in Spring Boot 3.x, including thread pinning when synchronized blocks combine with @Transactional, and ThreadLocal dependencies like SecurityContext or MDC in @Async methods.

When should I use deep review instead of a standard code review?▼

Use it for PRs marked critical, fixes for recurring bugs, changes touching transactions, security, or concurrency, and legacy code where real behavior is unclear. Standard review suffices for routine, low-risk changes with clear scope.

Related Skills

Explore More Software Engineering Skills→
christian-byrnechristian-byrne

ci-checker

Check GitHub CI status for pull requests and guide failure fixes.

Community
Advanced
ShmurdocShmurdoc

land-and-deploy

Merge pull requests, monitor CI pipelines, and verify production canary health.

Community
Advanced
robertphyattrobertphyatt
7

testing-theatre-detection

Detect missing assertions, excessive mocking, and swallowed errors in JavaScript and Python test suites.

Community
Advanced
NAMEWTANAMEWTA
2

observability-and-instrumentation

Add structured logs, metrics, and distributed tracing to production code.

Community
Intermediate