flutter-bug-triage

Diagnose wetty-chat Flutter client bugs by tracing Riverpod state and websocket flows.

17|10|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/chahua-im/chahua --skill flutter-bug-triage-chahua-im
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flutter-bug-triage
Source: https://github.com/chahua-im/chahua/tree/main/.agents/skills/flutter-bug-triage
Command: npx skills add https://github.com/chahua-im/chahua --skill flutter-bug-triage-chahua-im

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose and resolve bugs in the wetty-chat Flutter client by narrowing symptoms to the most likely layer, whether the issue is startup, auth, routing, state management, realtime sync, persistence, or rendering.

Core Features & Use Cases

  • Systematic Triage: Start from the visible symptom and trace it through widgets, Riverpod providers, services, and data stores.
  • Root Cause Analysis: Distinguish between UI display problems, stale state, websocket fan-out issues, reconciliation drift, and backend-dependent failures.
  • Reproducible Debugging: Produce concrete reproduction steps, targeted diagnostics, and verification guidance for fixes.
  • Use Case: A user reports that messages disappear after backgrounding the app, and this Skill helps isolate whether the bug comes from lifecycle recovery, websocket reconnect logic, or conversation state reconciliation.

Quick Start

Use this skill to investigate a wetty-chat Flutter bug, trace the failure path, and return a focused root-cause analysis with clear reproduction steps and fix guidance.

Frequently Asked Questions about flutter-bug-triage

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

FAQPage Schema
How do I debug a Flutter app where messages disappear after backgrounding?

Debug this Flutter issue by tracing the failure path through app lifecycle recovery, websocket reconnect logic, and Riverpod conversation state reconciliation to isolate the root cause and verify a targeted fix.

How does Riverpod state management affect Flutter bug triage?

Riverpod state management requires tracing provider dependencies and state mutations across widgets and services to distinguish UI display problems from stale state or backend-dependent websocket fan-out failures during triage.

What is the best way to isolate auth loop bugs in a Flutter client?

The best way to isolate auth loop bugs is to systematically triage from the visible symptom through routing, Riverpod providers, and networking layers to identify startup failures or backend-dependent recovery flow drift.

Can I use this to diagnose websocket realtime update failures across mobile and web?

Yes, you can diagnose websocket realtime update failures across mobile, desktop, and web by tracing websocket fan-out, recovery flows, and Riverpod state to distinguish reconciliation drift from backend-dependent failures.

Why does my Flutter routing navigation issue persist after state changes?

Your Flutter routing navigation issue persists because state changes may cause reconciliation drift between routing and Riverpod providers, requiring systematic root cause analysis to separate UI display problems from stale state.

What are the limitations of troubleshooting Flutter push notifications without backend logs?

Without backend logs, troubleshooting Flutter push notifications is limited to isolating client-side Riverpod state and websocket recovery flows, making it harder to distinguish frontend persistence bugs from backend-dependent failures.