Skip to main content 홈 크리에이터 jeremylongshore claude-code-plugins-plus-skills replit-debug-bundle
replit-debug-bundle Collect Replit diagnostic info for debugging deployments, workspace issues, and support tickets.
Use when encountering persistent issues, preparing support tickets,
or collecting system state for troubleshooting Replit problems.
Trigger with phrases like "replit debug", "replit support bundle",
"collect replit logs", "replit diagnostic", "replit troubleshoot".
설치로 이동 Skills Marketplace 커뮤니티가 만든 AI 스킬을 발견하고 탐색하세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill replit-debug-bundle명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Zip 다운로드 다운로드 중... 이 저장소의 다른 Skills Implement user sign-up and sign-in flows with Clerk.
Use when building authentication UI, customizing sign-in experience,
or implementing OAuth social login.
Trigger with phrases like "clerk sign-in", "clerk sign-up",
"clerk login flow", "clerk OAuth", "clerk social login".
Implement session management and middleware with Clerk.
Use when managing user sessions, configuring route protection,
or implementing token refresh and custom JWT templates.
Trigger with phrases like "clerk session", "clerk middleware",
"clerk route protection", "clerk token", "clerk JWT".
Configure enterprise SSO, role-based access control, and organization management.
Use when implementing SSO integration, configuring role-based permissions,
or setting up organization-level controls.
Trigger with phrases like "clerk SSO", "clerk RBAC",
"clerk enterprise", "clerk roles", "clerk permissions", "clerk organizations".
jeremylongshore
jeremylongshore/claude-code-plugins-plus-skills
GitHub 저장소 열기 name replit-debug-bundle description Collect Replit diagnostic info for debugging deployments, workspace issues, and support tickets.
Use when encountering persistent issues, preparing support tickets,
or collecting system state for troubleshooting Replit problems.
Trigger with phrases like "replit debug", "replit support bundle",
"collect replit logs", "replit diagnostic", "replit troubleshoot".
allowed-tools Read, Bash(grep:*), Bash(curl:*), Bash(tar:*), Grep version 1.12.0 license MIT author Jeremy Longshore <jeremy@intentsolutions.io> tags ["saas","replit","debugging","support"] compatibility Designed for Claude Code, also compatible with Codex and OpenClaw
Replit Debug Bundle
Current State
!node --version 2>/dev/null || echo 'Node: N/A'
!python3 --version 2>/dev/null || echo 'Python: N/A'
!echo "REPL_SLUG=$REPL_SLUG REPL_OWNER=$REPL_OWNER" 2>/dev/null || echo 'Not on Replit'
Overview
Collect all diagnostic information needed to debug Replit workspace, deployment, and database issues. Produces a redacted evidence bundle safe for sharing with Replit support.
Prerequisites
Shell access in Replit Workspace
Permission to read logs and configuration
Access to deployment monitoring (if deployed)
Instructions
Step 1: Automated Debug Bundle Script
#!/bin/bash
set -euo pipefail
BUNDLE="replit-debug-$(date +%Y%m%d-%H%M%S) "
mkdir -p "$BUNDLE " /{env ,db,config,network,packages}
echo "=== Replit Debug Bundle ===" > "$BUNDLE /summary.txt"
echo "Generated: $(date -u +%Y-%m-%dT%H:%M:%SZ) " >> "$BUNDLE /summary.txt"
echo "" >> "$BUNDLE /summary.txt"
echo "--- Runtime ---" >> "$BUNDLE /env/runtime.txt"
node --version >> "$BUNDLE /env/runtime.txt" 2>&1 || echo "Node: N/A" >> "$BUNDLE /env/runtime.txt"
python3 --version >> "$BUNDLE /env/runtime.txt" 2>&1 || echo "Python: N/A"
"$BUNDLE /env/runtime.txt"
uname
"$BUNDLE /env/runtime.txt"
echo
"--- Replit Env ---"
"$BUNDLE /env/replit-vars.txt"
echo
"REPL_SLUG=$REPL_SLUG "
"$BUNDLE /env/replit-vars.txt"
echo
"REPL_OWNER=$REPL_OWNER "
"$BUNDLE /env/replit-vars.txt"
echo
"REPL_ID=$REPL_ID "
"$BUNDLE /env/replit-vars.txt"
echo
"REPLIT_DB_URL=${REPLIT_DB_URL:+SET} "
"$BUNDLE /env/replit-vars.txt"
echo
"DATABASE_URL=${DATABASE_URL:+SET} "
"$BUNDLE /env/replit-vars.txt"
echo
"NODE_ENV=${NODE_ENV:-unset} "
"$BUNDLE /env/replit-vars.txt"
"$BUNDLE /packages/npm.txt"
true
"$BUNDLE /packages/pip.txt"
true
cp
"$BUNDLE /config/.replit"
echo
"No .replit"
"$BUNDLE /config/.replit"
cp
"$BUNDLE /config/replit.nix"
echo
"No replit.nix"
"$BUNDLE /config/replit.nix"
echo
"--- Database ---"
"$BUNDLE /db/status.txt"
if
"${DATABASE_URL:-} "
then
echo
"PostgreSQL: configured"
"$BUNDLE /db/status.txt"
"const {Pool}=require('pg');const p=new Pool({connectionString:process.env.DATABASE_URL,ssl:{rejectUnauthorized:false}});p.query('SELECT 1').then(()=>console.log('Connected')).catch(e=>console.log('Failed:',e.message)).finally(()=>p.end())"
"$BUNDLE /db/status.txt"
echo
"pg not installed"
"$BUNDLE /db/status.txt"
fi
if
"${REPLIT_DB_URL:-} "
then
echo
"Replit KV DB: configured"
"$BUNDLE /db/status.txt"
"$REPLIT_DB_URL ?prefix="
head
"$BUNDLE /db/kv-keys.txt"
echo
"KV DB unreachable"
"$BUNDLE /db/status.txt"
fi
echo
"--- Network ---"
"$BUNDLE /network/connectivity.txt"
"replit.com: HTTP %{http_code} (%{time_total}s)\n"
"$BUNDLE /network/connectivity.txt"
"status.replit.com: HTTP %{http_code} (%{time_total}s)\n"
"$BUNDLE /network/connectivity.txt"
df
"$BUNDLE /env/disk.txt"
du
"$BUNDLE /env/disk.txt"
head
"$BUNDLE /env/processes.txt"
"$BUNDLE .tar.gz"
"$BUNDLE "
echo
""
echo
"Debug bundle created: $BUNDLE .tar.gz"
echo
"Size: $(du -h "$BUNDLE .tar.gz" | cut -f1) "
rm
"$BUNDLE "
Step 2: Quick Health Check set -euo pipefail
echo "=== Quick Replit Health Check ==="
echo "Repl: $REPL_SLUG (owner: $REPL_OWNER )"
echo "Node: $(node --version 2>/dev/null || echo N/A) "
echo "Python: $(python3 --version 2>/dev/null || echo N/A) "
echo "DB URL: ${DATABASE_URL:+configured} "
echo "KV URL: ${REPLIT_DB_URL:+configured} "
echo "Disk: $(df -h / | tail -1 | awk '{print $3 "/" $2 " (" $5 " used)" }') "
curl -s -o /dev/null -w "Replit.com: %{http_code}\n" https://replit.com
curl -s https://status.replit.com/api/v2/summary.json 2>/dev/null | \
python3 -c "import sys,json;d=json.load(sys.stdin);print('Status:', d['status']['description'])" 2>/dev/null || echo "Status: check https://status.replit.com"
Step 3: Deployment-Specific Diagnostics set -euo pipefail
DEPLOY_URL="https://your-app.replit.app"
echo "=== Deployment Diagnostics ==="
curl -s -o /dev/null -w "Status: %{http_code}, Time: %{time_total}s\n" "$DEPLOY_URL /health"
curl -sI "$DEPLOY_URL " | grep -iE "^(server|x-replit|content-type|cache)"
echo "Cold start test (wait 5 min for sleep, then):"
echo "time curl -s $DEPLOY_URL /health"
Sensitive Data Handling ALWAYS REDACT before sharing:
API keys, tokens, passwords
DATABASE_URL connection strings
PII (emails, names, IDs)
REPL_IDENTITY tokens
Error messages and stack traces
Package versions
.replit and replit.nix contentsHTTP status codes and response times
Error Handling Item Purpose Safe to Share Runtime versions Compatibility check Yes Replit env vars (names only) Configuration status Yes Package list Dependency conflicts Yes Network latency Connectivity issues Yes Disk usage Storage problems Yes Connection strings Database access NEVER
Submit to Support
Create bundle: bash replit-debug-bundle.sh
Review for sensitive data
Open support ticket at https://replit.com/support
Attach the .tar.gz bundle
Include: steps to reproduce, expected vs actual behavior
Resources
Next Steps For rate limit issues, see replit-rate-limits.
