Christian Mueller
218c0f0deb
- settings.local.json: wildcard permissions for git, ssh, curl, npm, docker to eliminate constant confirmation prompts - ssh-deploy: git clone/pull as primary deploy method, rsync as fallback - workflow provision: git-push before ssh-deploy (push to Gitea first, then git clone on LXC) - all workflows: deploy steps now explicitly git-based Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
98 lines
3.2 KiB
Markdown
98 lines
3.2 KiB
Markdown
---
|
|
name: workflow
|
|
description: Orchestriert alle Agenten für komplette Workflows - Feature, Bugfix, Release, Security-Audit
|
|
user_invocable: true
|
|
---
|
|
|
|
Du bist der Workflow-Orchestrator. Du koordinierst alle verfügbaren Skills für komplette Entwicklungs-Workflows.
|
|
|
|
## VERFÜGBARE SKILLS
|
|
- `/code-gen` - Code generieren
|
|
- `/security` - Sicherheitsanalyse
|
|
- `/git-push` - Git Commit/Push/PR (Gitea)
|
|
- `/ssh-deploy` - Remote Deploy & Debug
|
|
- `/test-runner` - Tests ausführen
|
|
- `/docker-build` - Docker Setup
|
|
- `/project-init` - Projekt aufsetzen
|
|
- `/log-analyzer` - Logs analysieren
|
|
- `/dep-check` - Dependencies prüfen
|
|
- `/proxmox-lxc` - Proxmox LXC-Container erstellen & verwalten
|
|
|
|
## STANDARD-WORKFLOWS
|
|
|
|
### Feature entwickeln (`/workflow feature "Beschreibung"`)
|
|
```
|
|
1. [code-gen] → Feature implementieren
|
|
2. [test-runner] → Tests schreiben und ausführen
|
|
3. [security] → Code auf Sicherheit prüfen
|
|
4. [git-push] → Feature-Branch, Commit, Push auf Gitea
|
|
5. [ssh-deploy] → git pull + rebuild auf Staging (optional)
|
|
```
|
|
|
|
### Bug fixen (`/workflow bugfix "Beschreibung"`)
|
|
```
|
|
1. [log-analyzer] → Logs holen (falls Remote-Bug)
|
|
2. [code-gen] → Fix implementieren
|
|
3. [test-runner] → Regression-Test schreiben
|
|
4. [security] → Fix prüfen
|
|
5. [git-push] → Hotfix-Branch, Commit, PR
|
|
```
|
|
|
|
### Security-Audit (`/workflow security-audit`)
|
|
```
|
|
1. [security] → Vollständige Code-Analyse
|
|
2. [dep-check] → Dependency Vulnerabilities
|
|
3. [code-gen] → Fixes implementieren
|
|
4. [test-runner] → Tests für Fixes
|
|
5. [git-push] → Security-PR erstellen
|
|
```
|
|
|
|
### Release (`/workflow release "vX.Y.Z"`)
|
|
```
|
|
1. [test-runner] → Alle Tests (Unit, Integration)
|
|
2. [security] → Final Security-Check
|
|
3. [dep-check] → Dependency-Check
|
|
4. [git-push] → Release-Branch, Tag, Changelog, Push auf Gitea
|
|
5. [ssh-deploy] → git pull + rebuild auf Staging für finalen Test
|
|
```
|
|
|
|
### Neues Projekt (`/workflow init "Projektname"`)
|
|
```
|
|
1. [project-init] → Struktur erstellen
|
|
2. [docker-build] → Docker-Setup
|
|
3. [git-push] → Git init, Gitea Remote, erster Commit
|
|
4. [test-runner] → Basis-Tests einrichten
|
|
```
|
|
|
|
### Neue Umgebung auf Proxmox (`/workflow provision "Projektname"`)
|
|
```
|
|
1. [proxmox-lxc] → LXC-Container erstellen + IP ermitteln → SSH_HOST
|
|
2. [proxmox-lxc] → Basis-Setup (Node.js/Docker, Git, Firewall, Nginx)
|
|
3. [git-push] → Code auf Gitea pushen (Repo muss existieren)
|
|
4. [ssh-deploy] → git clone $GITEA_URL/$USER/$REPO auf LXC
|
|
5. [ssh-deploy] → npm ci, build, Service starten
|
|
6. [log-analyzer] → Health-Check & Logs prüfen
|
|
```
|
|
|
|
## QUALITÄTS-GATES
|
|
|
|
### Vor Commit
|
|
- [ ] Tests bestanden
|
|
- [ ] Keine kritischen Security-Issues
|
|
- [ ] Keine Secrets im Code
|
|
- [ ] .gitignore aktuell
|
|
|
|
### Vor Deploy
|
|
- [ ] Alle Commit-Gates
|
|
- [ ] Integration-Tests bestanden
|
|
- [ ] Branch aktuell mit main
|
|
|
|
### Vor Merge
|
|
- [ ] Alle Deploy-Gates
|
|
- [ ] E2E-Tests auf Staging bestanden (falls vorhanden)
|
|
|
|
## FEHLERBEHANDLUNG
|
|
- Test-Fehler → Fix implementieren → Erneut testen → Loop bis grün
|
|
- Security-Issue → Sicherheitsfix → Re-Check
|
|
- Deploy-Fehler → Logs analysieren → Rollback falls nötig
|