skills.rest
abnegate
abnegateCOMMUNITY
Explore all skills by this author →
GitHub

debug

Reproduce and fix failing Gradle tests and build errors in Java/Kotlin projects.

2|Updated Jan 22, 2026
Search Tags:#debugging#unit testing#root cause analysis#gradle#CI failures#test verification#git regression
One-click install
npx skills add https://github.com/abnegate/claudes --skill debug-abnegate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/abnegate/claudes/tree/main/skills/debug
Command: npx skills add https://github.com/abnegate/claudes --skill debug-abnegate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging failing tests, build errors, and runtime failures can be slow and confusing, especially when causes span recent changes, dependencies, or flaky behavior.

Core Features & Use Cases

  • Parallelized failure reproduction: Runs targeted Gradle test/build commands and captures complete error details (test name/class, stack trace, file/line, triggering inputs).
  • Parallelized root-cause analysis: Simultaneously inspects the failing test, the production code path it exercises, and related dependencies/mocks/config/DI wiring to form a root-cause hypothesis.
  • Aggressive iterative repair and verification: Implements a minimal targeted fix, re-runs the specific failing test and related tests in parallel, then performs full suite validation and adds coverage if needed.
  • Use Case: A CI pipeline fails after a refactor and you receive only a stack trace; use this skill to identify the regression or wiring issue, apply the minimal fix, and ensure the entire test suite passes.

Quick Start

Run the debug skill with a test name or error description so it can reproduce the issue, locate the root cause, apply a targeted fix, and confirm all tests pass.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I fix failing Gradle tests in a Java or Kotlin project?▼

Fix failing Gradle tests by running targeted ./gradlew test commands to reproduce the failure, inspecting the test and production code in parallel, applying a minimal fix, and verifying the full suite passes.

Why does my CI pipeline fail after a refactor with only a stack trace?▼

CI pipeline failures after a refactor often stem from regressions or wiring issues; inspect recent git changes and history alongside the stack trace to form a root-cause hypothesis and apply a targeted fix.

What is the best way to debug runtime errors and build failures in Gradle projects?▼

Debug runtime errors and build failures by reproducing the issue with targeted ./gradlew build commands, gathering complete error context, and inspecting related dependencies, mocks, and DI wiring to identify the root cause.

Can I use this to find the root cause of flaky test behavior across dependencies?▼

Yes, you can find the root cause of flaky behavior by inspecting the failing test, the production code path it exercises, and related dependencies or configuration simultaneously to form a root-cause hypothesis.

Does this debugging approach work with both Java and Kotlin Gradle projects?▼

Yes, this debugging approach works with Java and Kotlin Gradle projects, allowing you to run targeted test or build commands and inspect production code, dependencies, and git history to resolve failures.

How do I verify a targeted fix without running the entire test suite every time?▼

Verify a targeted fix by re-running the specific failing test and related tests in parallel after applying the minimal repair, then performing a full suite validation to ensure the original failure is resolved.

Related Skills

Explore More Software Engineering Skills→
semicolon-devteamsemicolon-devteam

test-patterns

Run Gradle unit, integration, and check tests for Spring Boot Kotlin projects.

Official
Advanced
kdlbskdlbs
562

fix

Reproduce bugs, identify root causes, and implement minimal fixes with regression tests.

Official
Intermediate
agent-shagent-sh
951

perf-theory-gatherer

Analyze git history and code evidence to propose performance hypotheses.

Official
Intermediate
ImaginerLabsImaginerLabs

debug-expert

Diagnose runtime errors and generate prioritized repair recommendations from stack traces and logs.

Official
Advanced