replit-debug-bundle

jeremylongshore's avatarfrom jeremylongshore

Collect Replit debug evidence for support tickets and troubleshooting.Use when encountering persistent issues, preparing support tickets,or collecting diagnostic information for Replit problems.Trigger with phrases like "replit debug", "replit support bundle","collect replit logs", "replit diagnostic".

⭐939stars🔀114forks📁View on GitHub🕐Updated Jan 11, 2026
[Debugging]

When & Why to Use This Skill

The Replit Debug Bundle skill is a specialized diagnostic tool designed to automate the collection of critical troubleshooting evidence. It streamlines the support process by gathering environment metadata, SDK versions, redacted system logs, and network connectivity status into a single, secure package, helping developers resolve Replit-specific issues faster and more effectively.

Use Cases

  • Preparing professional support tickets: Automatically generate a comprehensive diagnostic bundle to provide Replit support teams with all the context they need to resolve issues without back-and-forth questioning.
  • Troubleshooting persistent environment errors: Quickly identify runtime mismatches or configuration drifts by reviewing the consolidated environment and SDK summary.
  • Security-conscious log auditing: Collect and review application logs and environment variables with automatic redaction of sensitive API keys and secrets before sharing them for external help.
  • Network connectivity diagnostics: Run instant health checks against Replit APIs to determine if project issues are caused by local configuration or broader network connectivity problems.
namereplit-debug-bundle
description|
allowed-toolsRead, Bash(grep:*), Bash(curl:*), Bash(tar:*), Grep
version1.0.0
licenseMIT
authorJeremy Longshore <jeremy@intentsolutions.io>

Replit Debug Bundle

Overview

Collect all necessary diagnostic information for Replit support tickets.

Prerequisites

  • Replit SDK installed
  • Access to application logs
  • Permission to collect environment info

Instructions

Step 1: Create Debug Bundle Script

#!/bin/bash
# replit-debug-bundle.sh

BUNDLE_DIR="replit-debug-$(date +%Y%m%d-%H%M%S)"
mkdir -p "$BUNDLE_DIR"

echo "=== Replit Debug Bundle ===" > "$BUNDLE_DIR/summary.txt"
echo "Generated: $(date)" >> "$BUNDLE_DIR/summary.txt"

Step 2: Collect Environment Info

# Environment info
echo "--- Environment ---" >> "$BUNDLE_DIR/summary.txt"
node --version >> "$BUNDLE_DIR/summary.txt" 2>&1
npm --version >> "$BUNDLE_DIR/summary.txt" 2>&1
echo "REPLIT_API_KEY: ${REPLIT_API_KEY:+[SET]}" >> "$BUNDLE_DIR/summary.txt"

Step 3: Gather SDK and Logs

# SDK version
npm list @replit/sdk 2>/dev/null >> "$BUNDLE_DIR/summary.txt"

# Recent logs (redacted)
grep -i "replit" ~/.npm/_logs/*.log 2>/dev/null | tail -50 >> "$BUNDLE_DIR/logs.txt"

# Configuration (redacted - secrets masked)
echo "--- Config (redacted) ---" >> "$BUNDLE_DIR/summary.txt"
cat .env 2>/dev/null | sed 's/=.*/=***REDACTED***/' >> "$BUNDLE_DIR/config-redacted.txt"

# Network connectivity test
echo "--- Network Test ---" >> "$BUNDLE_DIR/summary.txt"
echo -n "API Health: " >> "$BUNDLE_DIR/summary.txt"
curl -s -o /dev/null -w "%{http_code}" https://api.replit.com/health >> "$BUNDLE_DIR/summary.txt"
echo "" >> "$BUNDLE_DIR/summary.txt"

Step 4: Package Bundle

tar -czf "$BUNDLE_DIR.tar.gz" "$BUNDLE_DIR"
echo "Bundle created: $BUNDLE_DIR.tar.gz"

Output

  • replit-debug-YYYYMMDD-HHMMSS.tar.gz archive containing:
    • summary.txt - Environment and SDK info
    • logs.txt - Recent redacted logs
    • config-redacted.txt - Configuration (secrets removed)

Error Handling

Item Purpose Included
Environment versions Compatibility check ✓
SDK version Version-specific bugs ✓
Error logs (redacted) Root cause analysis ✓
Config (redacted) Configuration issues ✓
Network test Connectivity issues ✓

Examples

Sensitive Data Handling

ALWAYS REDACT:

  • API keys and tokens
  • Passwords and secrets
  • PII (emails, names, IDs)

Safe to Include:

  • Error messages
  • Stack traces (redacted)
  • SDK/runtime versions

Submit to Support

  1. Create bundle: bash replit-debug-bundle.sh
  2. Review for sensitive data
  3. Upload to Replit support portal

Resources

Next Steps

For rate limit issues, see replit-rate-limits.