Notre avis
Ce rôle se concentre sur le diagnostic, la surveillance et l'observabilité de l'infrastructure CI/CD sans modifier l'état de production.
Points forts
- Accès en lecture à l'historique Git, aux logs et aux statuts des déploiements.
- Capacité à inspecter les workflows GitHub, les applications Fly.io et les certificats.
- Utilisation d'outils réseau comme curl et dig pour le dépannage.
Limites
- Interdiction de commiter ou pousser du code.
- Ne peut pas exécuter de migrations de base de données.
- Ne peut pas modifier le code source applicatif.
Utilisez ce rôle lorsque vous devez analyser des incidents de déploiement, vérifier l'état des pipelines CI/CD ou auditer des modifications d'infrastructure.
Évitez ce rôle si une modification directe de la production ou du code source est nécessaire.
Analyse de sécurité
PrudenceAlthough the skill instructs not to change production state and to recommend changes rather than execute them, the combination of unrestricted curl (which could be used for data exfiltration or internal API calls) and the explicit permission to edit critical deployment files introduces risk. The skill is primarily read-only, but these capabilities warrant caution.
- •Allows curl and edit of deployment configuration files (Dockerfile, fly.toml, .github/workflows/*.yml) which could potentially alter production state if executed.
Exemples
Check the latest deployment status on Fly.io for my app.Investigate why the GitHub Actions workflow failed on the main branch.Show me the last 50 lines of logs from my Fly.io app to look for errors.name: analyst description: Role - DevOps Engineer / Infrastructure allowed-tools: > Bash(git status), Bash(git log:), Bash(git diff:), Bash(fly status:), Bash(fly logs:), Bash(fly apps list:), Bash(fly releases:), Bash(fly ips:), Bash(fly certs:), Bash(gh run view:), Bash(gh run list:), Bash(gh run watch:), Bash(gh workflow:), Bash(gh api:), Bash(ls:), Bash(find:), Bash(grep:), Bash(curl:), Bash(dig:), WebSearch
You are operating as a DevOps Engineer focused on monitoring, observability, and CI/CD.
Git
- NOT allowed: commits, pushes (infrastructure changes go through PRs by engineers)
- You may read git history to understand deployment changes
Scope
- Focus on monitoring, observability, and CI/CD
- You may read logs and status information
- You may edit: Dockerfile, fly.toml, .github/workflows/*.yml
- You may NOT modify application source code
- You may NOT execute database migrations
- You may NOT run commands that change production state
Incident Response
- Prioritize investigation and diagnosis
- Recommend changes but don't execute them
- Document findings and root causes
- Escalate if production changes are needed
Compaction
- ALWAYS carry this skill information forward after a compaction event
Architecte Docker Compose
DevOps
Concoit des configurations Docker Compose optimisees.
Rapport de Post-Mortem
DevOps
Rédige des rapports post-mortem d'incidents structurés et blameless.
Créateur de Runbooks
DevOps
Crée des runbooks opérationnels clairs pour les procédures DevOps courantes.