deploy
Skill1 starsChanged 7 months agoMITView on GitHub
Go-Live Checkliste und Deployment. Nutze bei: 'deployen', 'go live', 'Production', 'Launch', 'Release', 'ist die App bereit', 'Deployment Checkliste'.
- Reads credentials
155 other projects use a version of this.
Adopted by
Most recently taken up by
- pedrohcgs/claude-code-my-workflowtheir own version, first seen Nov 8, 2026
- KingKongRobotics/jumpertheir own version, first seen Nov 8, 2026
- stakeme-team/arc-agent-kittheir own version, first seen Nov 8, 2026
- dockhold/mcptheir own version, first seen Nov 8, 2026
- KhaiTrang1995/nexus-kbtheir own version, first seen Nov 8, 2026
- ribato22/vibechecktheir own version, first seen Nov 8, 2026
Used with
Projects with it also use pm-discovery, qa-phase and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ww-w-aiSkillpm-discovery
PM Agent Team - Automated product discovery, strategy, and PRD generation. Runs PM analysis workflow to produce comprehensive PRD before PDCA Plan phase.
Also in 3 projects that use this
ww-w-aiSkillqa-phase
Run QA tests at various levels (L1-L5) for features under PDCA management. Integrates with MCP tools to execute structured test plans.
Also in 3 projects that use this
- +10 more from ww-w-ai
Other versions155 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 155
- ok-oldking/ok-wuthering-waves★ 8.6ksame name
- memovai/mimiclaw★ 5.8ksame name
- KingKongRobotics/jumper★ 3.1ksame name
- jhd3197/ServerKit★ 1.8ksame name
- pedrohcgs/claude-code-my-workflow★ 1.7ksame name
- mattmireles/gemma-tuner-multimodal★ 1.5ksame name
- microsoft/power-platform-skills★ 1.1ksame name
- jazzyalex/agent-sessions★ 941same name
- awslabs/agent-plugins★ 918same name
- patrickjaja/claude-desktop-extra★ 734same name
145 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- architectureSkill
- audit-projectSkill
- backendSkill
- docs-structureSkill
- frontendSkill
- geoSkill
- git-commitSkill
- helpSkill
- init-projectSkill
- laravel-a11ySkill
- laravel-docsSkill
- laravel-performanceSkill
- laravel-security-auditSkill
- laravel-testsSkill
- portfolio-texteSkill
- qaSkill
- requirementsSkill
- seoSkill
The file
Files
/deploy – Deployment & Go-Live
Du bist DevOps-Engineer. Du stellst sicher, dass das Deployment sauber läuft.
Vor dem Start
- QA-Status prüfen: Feature getestet? Keine kritischen Bugs?
- Tests: Alle grün?
- Build: Kompiliert fehlerfrei?
Falls QA nicht gemacht:
QA wurde noch nicht durchgeführt. Zuerst
/qaausführen.
Pre-Deployment Checklist
Code-Qualität
# Tests
php artisan test --parallel 2>/dev/null || npm test 2>/dev/null
# Lint
vendor/bin/pint --test 2>/dev/null || npm run lint 2>/dev/null
# Build
npm run build 2>/dev/null
php artisan view:cache 2>/dev/null- Alle Tests grün
- Linter ohne Fehler
- Build erfolgreich
- Kein
dd(),dump(),var_dump()im Code - Keine
console.log()in Production-JS - Code committed und gepusht
Umgebung (Laravel)
APP_ENV=productionAPP_DEBUG=falseAPP_KEYgesetzt (nicht der aus .env.example)APP_URLkorrekt (mit https://)LOG_LEVEL=warning(nicht debug)MAIL_MAILER=smtp(nicht log/mailtrap)SESSION_DRIVER=redis(nicht file)CACHE_STORE=redis(nicht file)QUEUE_CONNECTION=redis(nicht sync)
Datenbank
- Backup erstellt (BEVOR Migration!)
php artisan migrate --forceerfolgreich- Keine offenen Migrations die nicht committed sind
Security
- SSL-Zertifikat gültig
- HTTPS erzwungen (
URL::forceScheme('https')) - Mollie Live-Key (nicht test_)
.envnicht im Webroot erreichbar.envnicht in Git- Keine Secrets in Code hardcodiert
- Rate Limiting auf Login/API aktiv
Performance (Laravel)
php artisan config:cache
php artisan route:cache
php artisan view:cache
php artisan event:cache
php artisan optimizeQueue & Scheduler
- Horizon/Worker läuft (
php artisan horizon) - Supervisor/systemd konfiguriert (Auto-Restart)
- Scheduler in Crontab:
* * * * * php artisan schedule:run - Jobs verarbeiten korrekt (Horizon Dashboard prüfen)
Assets
npm run build(minified, versioned)- Keine lokalen Fonts/Scripts von externen CDNs (DSGVO!)
- Bilder optimiert (WebP/AVIF)
Deployment-Schritte
Laravel (typisch)
# 1. Maintenance Mode
php artisan down --retry=60
# 2. Code holen
git pull origin main
# 3. Dependencies
composer install --no-dev --optimize-autoloader
npm ci && npm run build
# 4. Migrationen
php artisan migrate --force
# 5. Cache
php artisan optimize
# 6. Queue restart
php artisan queue:restart
php artisan horizon:terminate # Supervisor startet neu
# 7. Online
php artisan upWordPress (typisch)
# 1. Backup (DB + Files)
# 2. Plugins deaktivieren
# 3. Updates einspielen (Core, Plugins, Theme)
# 4. Child-Theme prüfen
# 5. Plugins aktivieren
# 6. Cache leeren
# 7. TestenPost-Deployment
Sofort prüfen (erste 15 Minuten)
- Startseite lädt
- Login funktioniert
- Hauptfeature funktioniert (1x durchklicken)
- E-Mails werden versendet (Test-Mail)
- Queue verarbeitet Jobs (Horizon Dashboard)
- Keine Errors in Log (
tail -f storage/logs/laravel.log) - SSL funktioniert (kein Mixed Content)
Monitoring einrichten
- Error-Tracking (Sentry / Bugsnag)
- Uptime-Monitoring (UptimeRobot / Betterstack)
- Log-Rotation konfiguriert
- Backup-Schedule verifiziert
Rollback-Plan
Falls etwas schiefgeht:
# Laravel
php artisan down
git checkout {vorheriger-commit}
composer install --no-dev --optimize-autoloader
php artisan migrate:rollback
php artisan optimize
php artisan upErgebnis in Feature-Spec
## Deployment
**Deployed:** {YYYY-MM-DD}
**Umgebung:** Production
**URL:** {https://...}
**Status:** Live
**Rollback:** {commit-hash falls nötig}INDEX aktualisieren
Status des Features auf Done setzen.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

