from claude-code-plugins-plus-skills2,235
Step-by-step diagnostics and debugging techniques for deep Replit issues: Nix build failures, container crash loops, memory leaks, and platform vs app isolation
Provides a structured, layer-by-layer troubleshooting playbook and diagnostic scripts to investigate complex Replit failures. Includes a shell diagnostic (replit-diagnose.sh), guidance for Nix build debugging, crash-loop isolation steps, memory-leak detection hooks, and differences between workspace vs deployment behaviors. The skill helps engineers rapidly gather environment, resource, network, and log data to surface root causes.
Use when standard quick fixes fail: intermittent crashes, unexplained deployment failures, Nix build errors after dependency updates, unexplained memory growth in constrained containers, or when you need to separate platform-level outages from app bugs. Trigger phrases include: "replit hard bug", "replit mystery error", "replit intermittent", or "replit deep debug".
Best used with agents that can run shell/Node/Python snippets (Claude Code, Codex, Copilot-style assistants) or any environment where the agent can recommend and produce diagnostic scripts.
Replit advanced troubleshooting skill providing systematic diagnostics for Nix build failures, container crash loops, memory leaks, and platform-vs-app isolation. Well-structured with layered diagnostic script and practical code snippets for crash guards and memory monitoring. No bundled executable scripts — all code is inline in SKILL.md meant to be copy-pasted or adapted. Niche audience limited to Replit users with deep platform issues.
Solid diagnostic guide for Replit platform. No security concerns beyond the inherent risk of exposing debug endpoints in production, which the skill doesn't warn about. Code quality is good with proper error handling in the diagnostic script (set -euo pipefail, fallbacks on curl failures). Architecture follows a reasonable step-by-step structure but all code lives inline in SKILL.md with no scripts/ or references/ separation. Usefulness is limited — Replit-specific, advanced troubleshooting is a narrow use case.
