replit-incident-runbook

Execute Replit incident response procedures with triage, mitigation, and postmortem.Use when responding to Replit-related outages, investigating errors,or running post-incident reviews for Replit integration failures.Trigger with phrases like "replit incident", "replit outage","replit down", "replit on-call", "replit emergency", "replit broken".

⭐939stars🔀114forks📁View on GitHub🕐Updated Jan 11, 2026⬇️1downloads

When & Why to Use This Skill

The Replit Incident Runbook is a specialized Claude skill designed to streamline the end-to-end incident management process for Replit-based integrations. It empowers SREs and DevOps teams to rapidly triage outages, execute automated mitigation scripts via kubectl and curl, and manage stakeholder communication. By providing structured decision trees and remediation steps for common errors like rate limiting or authentication failures, it significantly reduces Mean Time to Recovery (MTTR) and ensures consistent post-incident documentation.

Use Cases

  • Real-time Triage: Quickly determine if a service disruption is caused by Replit's global status or internal configuration issues using automated health checks and status page monitoring.
  • Automated Mitigation: Execute immediate remediation actions such as rotating API keys, restarting Kubernetes pods, or enabling graceful degradation modes during high-latency events.
  • Incident Communication: Generate standardized, professional status updates for internal Slack channels and external status pages to keep stakeholders informed during critical outages.
  • Post-Incident Analysis: Automate the collection of logs, metrics, and evidence to populate postmortem templates, facilitating faster root cause identification and preventive action planning.
namereplit-incident-runbook
description|
allowed-toolsRead, Grep, Bash(kubectl:*), Bash(curl:*)
version1.0.0
licenseMIT
authorJeremy Longshore <jeremy@intentsolutions.io>

Replit Incident Runbook

Overview

Rapid incident response procedures for Replit-related outages.

Prerequisites

  • Access to Replit dashboard and status page
  • kubectl access to production cluster
  • Prometheus/Grafana access
  • Communication channels (Slack, PagerDuty)

Severity Levels

Level Definition Response Time Examples
P1 Complete outage < 15 min Replit API unreachable
P2 Degraded service < 1 hour High latency, partial failures
P3 Minor impact < 4 hours Webhook delays, non-critical errors
P4 No user impact Next business day Monitoring gaps

Quick Triage

# 1. Check Replit status
curl -s https://status.replit.com | jq

# 2. Check our integration health
curl -s https://api.yourapp.com/health | jq '.services.replit'

# 3. Check error rate (last 5 min)
curl -s localhost:9090/api/v1/query?query=rate(replit_errors_total[5m])

# 4. Recent error logs
kubectl logs -l app=replit-integration --since=5m | grep -i error | tail -20

Decision Tree

Replit API returning errors?
├─ YES: Is status.replit.com showing incident?
│   ├─ YES → Wait for Replit to resolve. Enable fallback.
│   └─ NO → Our integration issue. Check credentials, config.
└─ NO: Is our service healthy?
    ├─ YES → Likely resolved or intermittent. Monitor.
    └─ NO → Our infrastructure issue. Check pods, memory, network.

Immediate Actions by Error Type

401/403 - Authentication

# Verify API key is set
kubectl get secret replit-secrets -o jsonpath='{.data.api-key}' | base64 -d

# Check if key was rotated
# → Verify in Replit dashboard

# Remediation: Update secret and restart pods
kubectl create secret generic replit-secrets --from-literal=api-key=NEW_KEY --dry-run=client -o yaml | kubectl apply -f -
kubectl rollout restart deployment/replit-integration

429 - Rate Limited

# Check rate limit headers
curl -v https://api.replit.com 2>&1 | grep -i rate

# Enable request queuing
kubectl set env deployment/replit-integration RATE_LIMIT_MODE=queue

# Long-term: Contact Replit for limit increase

500/503 - Replit Errors

# Enable graceful degradation
kubectl set env deployment/replit-integration REPLIT_FALLBACK=true

# Notify users of degraded service
# Update status page

# Monitor Replit status for resolution

Communication Templates

Internal (Slack)

🔴 P1 INCIDENT: Replit Integration
Status: INVESTIGATING
Impact: [Describe user impact]
Current action: [What you're doing]
Next update: [Time]
Incident commander: @[name]

External (Status Page)

Replit Integration Issue

We're experiencing issues with our Replit integration.
Some users may experience [specific impact].

We're actively investigating and will provide updates.

Last updated: [timestamp]

Post-Incident

Evidence Collection

# Generate debug bundle
./scripts/replit-debug-bundle.sh

# Export relevant logs
kubectl logs -l app=replit-integration --since=1h > incident-logs.txt

# Capture metrics
curl "localhost:9090/api/v1/query_range?query=replit_errors_total&start=2h" > metrics.json

Postmortem Template

## Incident: Replit [Error Type]
**Date:** YYYY-MM-DD
**Duration:** X hours Y minutes
**Severity:** P[1-4]

### Summary
[1-2 sentence description]

### Timeline
- HH:MM - [Event]
- HH:MM - [Event]

### Root Cause
[Technical explanation]

### Impact
- Users affected: N
- Revenue impact: $X

### Action Items
- [ ] [Preventive measure] - Owner - Due date

Instructions

Step 1: Quick Triage

Run the triage commands to identify the issue source.

Step 2: Follow Decision Tree

Determine if the issue is Replit-side or internal.

Step 3: Execute Immediate Actions

Apply the appropriate remediation for the error type.

Step 4: Communicate Status

Update internal and external stakeholders.

Output

  • Issue identified and categorized
  • Remediation applied
  • Stakeholders notified
  • Evidence collected for postmortem

Error Handling

Issue Cause Solution
Can't reach status page Network issue Use mobile or VPN
kubectl fails Auth expired Re-authenticate
Metrics unavailable Prometheus down Check backup metrics
Secret rotation fails Permission denied Escalate to admin

Examples

One-Line Health Check

curl -sf https://api.yourapp.com/health | jq '.services.replit.status' || echo "UNHEALTHY"

Resources

Next Steps

For data handling, see replit-data-handling.