skills.rest
nirukk52
nirukk52COMMUNITY
Explore all skills by this author →
GitHub

backend-debugging

Diagnose Encore.ts backend failures using logs, SQL queries, and diagnostic scripts.

1|Updated Oct 23, 2025
Search Tags:#testing#logs#diagnostics#rca#Encore#backend-debugging
One-click install
npx skills add https://github.com/nirukk52/ScreenGraph --skill backend-debugging
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backend-debugging
Source: https://github.com/nirukk52/ScreenGraph/tree/main/.claude-skills/backend-debugging_skill
Command: npx skills add https://github.com/nirukk52/ScreenGraph --skill backend-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systematic debugging for Encore.ts backend incidents using diagnostic scripts, targeted queries, and structured logging to restore flows quickly.

Core Features & Use Cases

  • Reproduce failures and capture context from tests and logs
  • Use targeted SQL queries to inspect database state
  • Run diagnostic scripts and use RCA playbooks to identify root causes
  • Document root cause and remediation in Graphiti for future prevention

Quick Start

When a backend issue arises, follow the rapid response workflow:

  1. Reproduce failure with encore test
  2. Inspect DB with diagnostic queries
  3. Run diagnostic scripts from the reference library
  4. Document RCA and remediation in Graphiti

Frequently Asked Questions about backend-debugging

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

FAQPage Schema
How do I debug backend failures in Encore.ts using logs and diagnostics?▼

Diagnose Encore.ts backend failures by reproducing the issue with encore test, analyzing structured logs from encore.dev/log (module, actor, runId), running targeted SQL queries to inspect database state, and applying diagnostic scripts from the reference library to identify root cause.

What's the best way to troubleshoot flaky integration tests in Encore?▼

Flaky integration tests improve by importing all Pub/Sub workers in tests, replacing fixed sleeps with polling loops and timeouts, and using structured logging to capture context. Run diagnostic scripts to isolate timing or state issues causing intermittent failures.

How do I set up structured logging for backend debugging in Encore.ts?▼

Structured logging in Encore uses encore.dev/log with module, actor, and runId fields to tag log entries. This enables targeted filtering and correlation across requests, making it easier to trace failures through logs and reconstruct incident context during RCA.

Can I use diagnostic queries to inspect database state during backend incidents?▼

Yes. Targeted SQL queries let you inspect database state and verify data consistency during incidents. Combined with structured logs and diagnostic scripts, queries provide evidence for root cause analysis and confirm fixes before redeployment.

What problems does systematic backend debugging solve for CI regressions?▼

Systematic debugging applies to CI regressions, stalled workers, and subscription issues by capturing logs, running reproducible tests, and executing diagnostic scripts. Documenting findings in RCA playbooks prevents recurrence and accelerates future incident response.

Related Skills

Explore More Software Engineering Skills→
encoredevencoredev
26

encore-go-testing

Run Encore Go tests for APIs, databases, and pub/sub flows.

Official
Advanced
rbah31rbah31
5

runbook

Investigate production symptoms and generate structured incident reports from logs, metrics, and traces.

Community
Intermediate
Jaydpatel01Jaydpatel01

incident-response-and-debugging

Diagnose production incidents using phased response protocols and debugging techniques.

Community
Advanced
thoreinsteinthoreinstein
5

postmortem

Generates blameless postmortems with root-cause analysis for software incidents.

Community
Advanced