serverless-debugging

Diagnose missing serverless and edge function logs across database, code, runtime, and environment layers.

1|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/mealpac/manus --skill serverless-debugging
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: serverless-debugging
Source: https://github.com/mealpac/manus/tree/main/skills/development-skills/serverless-debugging
Command: npx skills add https://github.com/mealpac/manus --skill serverless-debugging

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 serverless and edge functions when standard logs are missing or unreliable, enabling precise problem isolation and faster recovery.

Core Features & Use Cases

  • Evidence gathering across the Database, Code, Runtime, and Environment layers to ground hypotheses.
  • Pattern analysis to differentiate working vs broken behavior and identify root causes.
  • Hypothesis formation with testable, verifiable bets and minimal repros.
  • Implementation and verification through targeted fixes, minimal changes, and cross-layer validation.
  • Alternative debugging strategies such as database-driven logging, diagnostic endpoints, and structured logs.
  • Practical tools and references for deployment verification, database state checks, and type analysis.

Quick Start

Run the evidence checklist and execute the provided scripts to reproduce issues, test hypotheses, and verify fixes end-to-end.

Frequently Asked Questions about serverless-debugging

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

FAQPage Schema
How do I debug serverless functions when logs are missing?โ–ผ

Debug serverless functions with missing logs by applying a 4-phase methodology across database, code, runtime, and environment layers to gather evidence, form testable hypotheses, and verify fixes.

What is the best way to diagnose edge function behavioral discrepancies in production?โ–ผ

Diagnose edge function discrepancies in production by running an evidence checklist and executing diagnostic scripts to differentiate working versus broken behavior, isolating the root cause without relying on standard logs.

Why does my serverless function fail in production but work locally?โ–ผ

Serverless functions fail in production due to environment or database state differences; perform cross-layer validation and database state checks to reproduce the exact behavioral discrepancy and identify the mismatch.

What alternative strategies exist for serverless observability when standard logs vanish?โ–ผ

Alternative serverless observability strategies include database-driven logging, deploying diagnostic endpoints, and implementing structured logs to capture execution evidence when standard logging fails.

Can I use diagnostic scripts to verify serverless deployment state?โ–ผ

Yes, you can execute the included diagnostic scripts to verify serverless deployment state, analyze types, and validate that targeted fixes resolve behavioral discrepancies end-to-end.

How to reproduce serverless issues without reliable production logs?โ–ผ

Reproduce serverless issues by running the evidence checklist to gather data across environment and runtime layers, then constructing minimal reproductions to test verifiable bets against the broken behavior.