Skill

replit-debug-bundle

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".

From replit-pack

Install

Run in your terminal

npx claudepluginhub nickloveinvesting/nick-love-plugins --plugin replit-pack

Tool Access

This skill is limited to using the following tools:

ReadBash(grep:*)Bash(curl:*)Bash(tar:*)Grep

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.6k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

evaluation-methodology

1 file

Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.

plugin-eval

32.9k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 20, 2026

Actions

View Source View Plugin View on GitHub View README

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

set -euo pipefail
# 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

set -euo pipefail
# 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

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

Resources

Next Steps

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