skills.rest
jpmoya
jpmoyaCOMMUNITY
Explore all skills by this author →
GitHub

fullstack-bug-fixing

Diagnose and fix bugs in React, FastAPI, and Capacitor apps through a six-phase root-cause workflow.

Updated Sep 1, 2026
Search Tags:#debugging#react#pydantic#fastapi#root cause analysis#regression testing#capacitor
One-click install
npx skills add https://github.com/jpmoya/claude-agents --skill fullstack-bug-fixing-jpmoya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fullstack-bug-fixing
Source: https://github.com/jpmoya/claude-agents/tree/main/skills/fullstack-bug-fixing
Command: npx skills add https://github.com/jpmoya/claude-agents --skill fullstack-bug-fixing-jpmoya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Full-stack bugs often get patched at the symptom level, causing regressions, silent data corruption, and recurring incidents. This Skill enforces a disciplined reproduce-root-cause-test-fix-verify process so fixes address the actual cause across the React frontend, FastAPI backend, and Capacitor native layers. ## Core Features & Use Cases - Six-phase debugging workflow: Goal gate, reproduce, root cause, failing test (red), minimal fix (green), and production verification, with a ratchet rule that reverts failed attempts instead of stacking fixes. - Full-stack trap catalog: Documented patterns for Pydantic default-fill data wipes, validation failure cascades, React stale closures, fetch race conditions, falsy-value guards, and mock shape drift. - Capacitor cross-platform guidance: Covers Firebase Auth hangs in WKWebView, per-platform CORS origins, UNIMPLEMENTED plugin errors, and static export gotchas for iOS/Android builds. - Use Case: A user reports their nutrition goals were wiped after a partial profile update. The Skill guides you to reproduce against stored data, trace the Pydantic wholesale-replacement bug, write a failing test proving sibling fields are lost, apply a model_copy merge fix, and verify with a data repair migration. ## Quick Start Use the fullstack-bug-fixing skill to investigate why profile data disappears after a partial update in my React and FastAPI app.

Frequently Asked Questions about fullstack-bug-fixing

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

FAQPage Schema
How do I debug a full-stack bug in a React and FastAPI app?▼

Follow a six-phase process: define the goal, reproduce the symptom, trace the root cause across the React-to-FastAPI-to-database boundary, write a failing test, apply a minimal fix, then verify in production. Never fix before identifying the root cause.

Why does a Pydantic partial update wipe other fields?▼

Pydantic models fill defaults for unset fields, so replacing a nested object wholesale zeros any fields the client did not send. Use model_copy with update set to model_dump(exclude_unset=True) to merge only the submitted fields.

Why does Firebase getAuth hang on Capacitor iOS?▼

Firebase getAuth assumes a browser context and hangs silently inside the Capacitor WKWebView. On native platforms, use initializeAuth with indexedDBLocalPersistence instead, keeping getAuth only for web builds.

Why does my app work on web but fail on iOS or Android?▼

Cross-platform failures usually come from the Capacitor bridge, CORS origins, or persistence. Ensure the backend allows capacitor://localhost, https://localhost, and your dev origin, and check Xcode or Logcat for native errors that never reach JavaScript.

How do I prevent React fetch race conditions in useEffect?▼

Use an AbortController in the useEffect cleanup function so stale requests are cancelled when dependencies change. Without cancellation, an older response can arrive last and overwrite newer, correct data.

When should I stop retrying a fix and rethink the approach?▼

Stop after three failed fix attempts. Revert each failed attempt with git stash or reset rather than stacking fixes, then question the architecture itself, since repeated failure indicates the pattern is wrong, not just the implementation.

Related Skills

Explore More Software Engineering Skills→
jonkikyjonkiky

investigate

Trace reported issue symptoms to code paths and verify root cause hypotheses.

Community
Advanced
ChegginCheggin
1

incident-response

Detect downtime incidents, diagnose root causes, and coordinate fixes with budget guards.

Community
Advanced
Coverage-CreativesCoverage-Creatives

Debug

Diagnose software defects through root cause analysis and resolution verification.

Official
Advanced
huanlongAIhuanlongAI

systematic-debugging

Trace root causes through a four-phase debugging workflow.

Official
Advanced