skills.rest
taucao-ruby
taucao-rubyCOMMUNITY
Explore all skills by this author →
𝕏@winter_sunshinGitHub

soleil-ai-review-engine-debugging

Trace software bugs by querying execution paths and inspecting caller relationships.

Updated Aug 27, 2026
Search Tags:#debugging#error-analysis#ai-assisted#code-trace#execution-flow#callers-callees
One-click install
npx skills add https://github.com/taucao-ruby/soleil-hostel --skill soleil-ai-review-engine-debugging
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: soleil-ai-review-engine-debugging
Source: https://github.com/taucao-ruby/soleil-hostel/tree/main/.claude/skills/soleil-ai-review-engine/soleil-ai-review-engine-debugging
Command: npx skills add https://github.com/taucao-ruby/soleil-hostel --skill soleil-ai-review-engine-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly diagnose bugs and trace errors by querying execution paths, revealing callers and callees, and surfacing context needed to fix failures.

Core Features & Use Cases

  • Query related execution flows with soleil-ai-review-engine_query to surface error patterns.
  • Inspect caller/callee relationships and process context with soleil-ai-review-engine_context.
  • Read detailed trace through soleil-ai-review-engine://repo/{name}/process/{name} to understand data flow.
  • Build custom traces when needed using soleil-ai-review-engine_cypher for targeted investigations.
  • Use the workflow to investigate endpoints returning errors, intermittent failures, or regressions in a codebase.

Quick Start

Describe the bug or error and run soleil-ai-review-engine_query with the exact error text to begin the investigation.

Frequently Asked Questions about soleil-ai-review-engine-debugging

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

FAQPage Schema
How do I trace the root cause of an exception spanning multiple functions?▼

Trace the root cause of an exception by querying execution paths with the exact error text to surface patterns, then inspect caller and callee relationships to reveal the multi-function context needed to fix the failure.

What is the best way to debug a failed endpoint returning unexpected behavior?▼

Debug a failed endpoint by describing the bug and querying execution flows to surface error patterns. You can then inspect process context and read detailed traces to understand the data flow causing the unexpected behavior.

How does automated querying help investigate intermittent failures or regressions?▼

Automated querying investigates intermittent failures or regressions by applying a structured workflow to gather evidence across services, inspecting process context and data flow to pinpoint the root cause fast.

Can I build custom traces for targeted error analysis investigations?▼

Yes, you can build custom traces for targeted error analysis using custom queries. This allows you to perform targeted investigations into specific execution flows when default querying does not surface enough evidence.

What context do I need to provide to start diagnosing bugs in a software project?▼

To start diagnosing bugs in a software project, you need to provide a description of the bug or error. Running a query with the exact error text initiates the investigation and surfaces relevant execution paths.

Related Skills

Explore More Software Engineering Skills→
bettercallzaalbettercallzaal
1

gitnexus-debugging

Query GitNexus to locate error sources and trace execution paths.

Community
Advanced
jagreehaljagreehal
3

code-flow-analysis

Trace code execution paths through fn(args, deps) flows and Result propagation.

Community
Advanced
anukkrit149anukkrit149

gitnexus-exploring

Trace end-to-end execution flows in indexed codebases using gitnexus queries.

Community
Intermediate
JonghakseoJonghakseo
13

systematic-debugging

Trace data flow and test hypotheses to identify root causes of bugs.

Community
Advanced