backend-debug

Debug FastAPI backend issues on GCP Cloud Run with PostgreSQL.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Youngger9765/career-creator --skill backend-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-debug
Source: https://github.com/Youngger9765/career-creator/tree/main/.claude/skills/backend-debug
Command: npx skills add https://github.com/Youngger9765/career-creator --skill backend-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a structured approach to debugging backend API errors, database issues, and deployment failures, ensuring quick resolution and minimal downtime.

Core Features & Use Cases

  • Systematic Debugging: Follows a step-by-step process from reproducing the error to root cause analysis and verification.
  • Evidence Collection: Automatically gathers API responses, logs, and database states for thorough analysis.
  • Use Case: When a user reports a 500 error on the staging API, this Skill can be invoked with the issue number to systematically reproduce the error, analyze logs, identify the faulty code, fix it, and verify the solution.

Quick Start

Use the backend-debug skill to debug issue number 123.

Frequently Asked Questions about backend-debug

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

FAQPage Schema
How do I debug a FastAPI application deployed on GCP Cloud Run?

Debugging a FastAPI application on GCP Cloud Run requires reproducing the error, analyzing evidence from API responses and Cloud Run logs, performing root cause analysis with the 5-Why method, and verifying the fix.

What is the best way to find the root cause of a 500 error in a backend API?

Finding the root cause of a 500 error involves analyzing evidence from API responses and Cloud Run logs, then applying the 5-Why method to systematically identify the underlying fault.

How do I reproduce and analyze PostgreSQL database issues in a staging API?

Reproducing and analyzing PostgreSQL database issues in a staging API involves triggering the error, gathering database states and API response evidence, and analyzing Cloud Run logs to pinpoint the fault.

Does this debugging workflow require documenting issues on GitHub?

Yes, the debugging workflow mandates comprehensive documentation of all debugging steps, evidence, and findings in GitHub Issues to ensure traceability and quick resolution.

Can I use this systematic approach for deployment failures on GCP Cloud Run?

Yes, you can use this systematic approach for deployment failures on GCP Cloud Run. It guides you through evidence collection, root cause analysis, and verification to resolve backend deployment issues.