replit-ci-integration
Configure CI/CD for Replit with GitHub Actions, automated testing, and deploy-on-push. Use when setting up automated testing, GitHub integration for Replit, or continuous deployment pipelines that deploy to Replit. Trigger with phrases like "replit CI", "replit GitHub Actions", "replit automated deploy", "CI replit", "replit GitHub".
Best use case
replit-ci-integration is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Configure CI/CD for Replit with GitHub Actions, automated testing, and deploy-on-push. Use when setting up automated testing, GitHub integration for Replit, or continuous deployment pipelines that deploy to Replit. Trigger with phrases like "replit CI", "replit GitHub Actions", "replit automated deploy", "CI replit", "replit GitHub".
Teams using replit-ci-integration should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/replit-ci-integration/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How replit-ci-integration Compares
| Feature / Agent | replit-ci-integration | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Configure CI/CD for Replit with GitHub Actions, automated testing, and deploy-on-push. Use when setting up automated testing, GitHub integration for Replit, or continuous deployment pipelines that deploy to Replit. Trigger with phrases like "replit CI", "replit GitHub Actions", "replit automated deploy", "CI replit", "replit GitHub".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# Replit CI Integration
## Overview
Set up CI/CD for Replit apps: GitHub repo connected to Replit, automated testing via GitHub Actions, deploy-on-push, and post-deploy health verification. Replit supports direct GitHub import and auto-sync.
## Prerequisites
- GitHub repository with Actions enabled
- Replit App connected to GitHub (Settings > Git > Connect)
- GitHub Secrets configured for deploy verification
## Instructions
### Step 1: Connect Replit to GitHub
```markdown
1. In your Repl, click "Git" in the sidebar
2. Click "Connect to GitHub"
3. Authorize Replit GitHub App
4. Select your repository
5. Changes pushed to GitHub auto-sync to Replit
Alternative: Import from GitHub
1. Create new Repl > "Import from GitHub"
2. Paste repo URL
3. Replit clones and configures automatically
```
### Step 2: GitHub Actions — Test on PR
```yaml
# .github/workflows/test.yml
name: Test
on:
push:
branches: [main]
pull_request:
branches: [main]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'npm'
- run: npm ci
- run: npm test -- --coverage
- run: npm run lint
- run: npm run build
```
### Step 3: Deploy Verification After Push
Replit auto-deploys when you push to the connected branch. Verify the deployment is healthy:
```yaml
# .github/workflows/deploy-verify.yml
name: Verify Deployment
on:
push:
branches: [main]
jobs:
verify:
runs-on: ubuntu-latest
# Wait for Replit to pick up the push and deploy
steps:
- name: Wait for deployment
run: sleep 60
- name: Health check
run: |
DEPLOY_URL="${{ secrets.REPLIT_DEPLOY_URL }}"
STATUS=$(curl -s -o /dev/null -w "%{http_code}" "$DEPLOY_URL/health")
if [ "$STATUS" != "200" ]; then
echo "Health check failed: HTTP $STATUS"
exit 1
fi
echo "Deployment healthy"
- name: Response time check
run: |
DEPLOY_URL="${{ secrets.REPLIT_DEPLOY_URL }}"
TIME=$(curl -s -o /dev/null -w "%{time_total}" "$DEPLOY_URL/health")
echo "Response time: ${TIME}s"
# Alert if response > 5 seconds (cold start)
if (( $(echo "$TIME > 5" | bc -l) )); then
echo "WARNING: Slow response (possible cold start)"
fi
```
### Step 4: Store Deployment Secrets
```bash
# Set GitHub secrets for deploy verification
gh secret set REPLIT_DEPLOY_URL --body "https://your-app.replit.app"
# Optional: Replit API token for advanced deployments
gh secret set REPLIT_TOKEN --body "your-replit-api-token"
```
### Step 5: Branch Protection
```yaml
# Require tests to pass before merge
# In GitHub: Settings > Branches > Branch protection rules
# Required status checks:
required_status_checks:
- "test"
# Recommended settings:
# - Require pull request reviews before merging
# - Require status checks to pass before merging
# - Require branches to be up to date before merging
```
### Step 6: GitHub Actions — Deploy from GitHub Repo
For repos not directly connected to Replit, deploy via GitHub Import:
```yaml
# .github/workflows/deploy-replit.yml
name: Deploy to Replit
on:
push:
branches: [main]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Run tests first
run: |
npm ci
npm test
npm run build
- name: Trigger Replit deployment
run: |
# Replit auto-deploys from connected GitHub repos
# For manual trigger, use Replit API:
curl -X POST \
"https://replit.com/api/v1/repls/${{ secrets.REPL_ID }}/deploy" \
-H "Authorization: Bearer ${{ secrets.REPLIT_TOKEN }}" \
-H "Content-Type: application/json"
- name: Verify deployment
run: |
sleep 90 # Wait for build + deploy
curl -sf "${{ secrets.REPLIT_DEPLOY_URL }}/health"
```
### Step 7: Python CI Variant
```yaml
# .github/workflows/test-python.yml
name: Test Python
on: [push, pull_request]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-python@v5
with:
python-version: '3.11'
cache: 'pip'
- run: pip install -r requirements.txt
- run: python -m pytest tests/ -v
- run: python -m flake8 .
```
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| GitHub sync not working | App not connected | Reconnect in Replit Git settings |
| Deploy verification timeout | Slow Autoscale cold start | Increase sleep, or use Reserved VM |
| Tests pass but deploy fails | Build step missing | Add `build` to `.replit` deployment section |
| Secret not found in Actions | Not set in GitHub | `gh secret set` with correct name |
## Resources
- [Deploying from GitHub](https://docs.replit.com/hosting/deployments/deploying-a-github-repository)
- [GitHub Actions](https://docs.github.com/en/actions)
- [Replit Git Integration](https://docs.replit.com/replit-workspace/configuring-repl)
## Next Steps
For deployment patterns, see `replit-deploy-integration`.Related Skills
running-integration-tests
Execute integration tests validating component interactions and system integration. Use when performing specialized testing. Trigger with phrases like "run integration tests", "test integration", or "validate component interactions".
workhuman-deploy-integration
Workhuman deploy integration for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman deploy integration".
workhuman-ci-integration
Workhuman ci integration for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman ci integration".
wispr-deploy-integration
Wispr Flow deploy integration for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr deploy integration".
wispr-ci-integration
Wispr Flow ci integration for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr ci integration".
windsurf-ci-integration
Integrate Windsurf Cascade workflows into CI/CD pipelines and team automation. Use when automating Cascade tasks in GitHub Actions, enforcing AI code quality gates, or setting up Windsurf config validation in CI. Trigger with phrases like "windsurf CI", "windsurf GitHub Actions", "windsurf automation", "cascade CI", "windsurf pipeline".
webflow-deploy-integration
Deploy Webflow-powered applications to Vercel, Fly.io, and Google Cloud Run with proper secrets management and Webflow-specific health checks. Trigger with phrases like "deploy webflow", "webflow Vercel", "webflow production deploy", "webflow Cloud Run", "webflow Fly.io".
webflow-ci-integration
Configure Webflow CI/CD with GitHub Actions — automated CMS validation, integration tests with test tokens, and publish-on-merge workflows. Use when setting up automated testing or CI pipelines for Webflow integrations. Trigger with phrases like "webflow CI", "webflow GitHub Actions", "webflow automated tests", "CI webflow", "webflow pipeline".
vercel-deploy-integration
Deploy and manage Vercel production deployments with promotion, rollback, and multi-region strategies. Use when deploying to production, configuring deployment regions, or setting up blue-green deployment patterns on Vercel. Trigger with phrases like "deploy vercel", "vercel production deploy", "vercel promote", "vercel rollback", "vercel regions".
veeva-deploy-integration
Veeva Vault deploy integration for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva deploy integration".
veeva-ci-integration
Veeva Vault ci integration for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva ci integration".
vastai-deploy-integration
Deploy ML training jobs and inference services on Vast.ai GPU cloud. Use when deploying GPU workloads, configuring Docker images, or setting up automated deployment scripts. Trigger with phrases like "deploy vastai", "vastai deployment", "vastai docker", "vastai production deploy".