r-shiny-debugging

Name: r-shiny-debugging
Availability: InStock
Author: blankuzr

Trace Shiny reactive-state failures through the dependency graph.

6|Updated Apr 8, 2026

Search Tags:#workflow #testing #ui #debugging #reactivity #module #shiny

Ready to run

npx skills add https://github.com/blankuzr/R-Skills --skill r-shiny-debugging

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: r-shiny-debugging
Source: https://github.com/blankuzr/R-Skills/tree/main/gpt/skills/r-shiny-debugging
Command: npx skills add https://github.com/blankuzr/R-Skills --skill r-shiny-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Diagnose Shiny bugs by narrowing the reactive path, inspecting the structure and dependency layer, stabilizing input updates, and reproducing the failure in a module test.

Core Features & Use Cases

Diagnose reactive loops, stale outputs, dynamic UI, background tasks, maps, tables, and plots.
Inspect the dependency graph and failure path to guide fixes across modules and tests.
Support accessibility checks and module-boundaries to ensure robust, maintainable Shiny apps.

Quick Start

Reproduce the bug with the smallest possible click path and viewport, then consult the references to guide diagnosis.

Frequently Asked Questions about r-shiny-debugging

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

FAQPage Schema

How do I debug reactive loops and stale outputs in a Shiny app?▼

To debug Shiny reactive loops and stale outputs, trace the failure path from inputs to outputs through the dependency graph. You can stabilize input updates and reproduce the specific failure within a module test to isolate and guide fixes.

What is the best way to trace a Shiny reactivity failure across modules?▼

The best way to trace a Shiny reactivity failure across modules is to inspect the dependency graph and failure path. Reproduce the bug with the smallest possible click path and viewport, then use reference-guided diagnostics to map dependencies.

Can I use this debugging workflow for Shiny apps with dynamic UI and background tasks?▼

Yes, this debugging workflow can be used for Shiny apps with dynamic UI and background tasks. It diagnoses reactive state bugs across modular applications, handling complex scenarios involving maps, tables, plots, and accessibility checks.

How do I reproduce a Shiny bug to inspect its dependency layer?▼

To reproduce a Shiny bug and inspect its dependency layer, recreate the failure using the smallest possible click path and viewport. This minimizes variables, allowing you to stabilize inputs and accurately trace dependencies through module-tested scenarios.

Why does my Shiny app show stale outputs after dynamic UI updates?▼

Shiny apps show stale outputs after dynamic UI updates when reactive dependencies are not properly invalidated. Diagnose this by inspecting the dependency graph to ensure inputs stabilize and trigger the correct reactive path through reference-guided diagnostics.