debugging

Diagnose backend, frontend, and database issues across the Shorted project.

3|Updated Jan 22, 2024
One-click install
npx skills add https://github.com/castlemilk/shorted.com.au --skill debugging-castlemilk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/castlemilk/shorted.com.au/tree/main/.claude/skills/debugging
Command: npx skills add https://github.com/castlemilk/shorted.com.au --skill debugging-castlemilk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging tasks across the Shorted project to locate and fix issues in backend, frontend, and database.

Core Features & Use Cases

  • System-wide diagnostics: step through common failure points and reproduce issues across services.
  • Environment & health checks: verify containers, ports, and DB connections to validate system readiness.
  • Guided triage workflows: provide reproducible debugging sequences with commands and checks.

Quick Start

Start the full local environment with make dev and monitor frontend, backend, and database logs to reproduce and diagnose issues.

Frequently Asked Questions about debugging

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

FAQPage Schema
How do I debug backend, frontend, and database issues in the Shorted project?

Debug Shorted project issues by running make dev to start the local environment, then inspect frontend, backend, and database logs to reproduce and diagnose failures using step-by-step triage workflows and environment health checks.

What's the best way to verify containers and DB connections before diagnosing Shorted errors?

Verify system readiness by running environment and health checks that validate containers, ports, and DB connections, ensuring the Shorted project infrastructure is fully operational before deeper troubleshooting.

Can I use psql and docker commands to step through Shorted project failure points?

Yes, use psql and docker commands to execute reproducible debugging sequences that step through common Shorted project failure points, validating environment health and resolving backend, frontend, and database issues.

Why does my Shorted deployment fail and how do I inspect logs to find the bottleneck?

Shorted deployments may fail due to backend errors, performance bottlenecks, or database connection issues; inspect frontend, backend, and database logs using make and docker commands to identify and resolve the root cause.

Does this debugging workflow cover production triage or is it only for local development?

This debugging workflow is applicable during development, testing, and production triage, providing reproducible diagnostic sequences and environment checks to resolve errors, performance bottlenecks, and deployment failures across the Shorted project.