Silence render-disposed spam, unbreak bundled skills, drop board wake

Three independently ugly bugs that all fed the same log flood: * Electron's `WebFrameMain.send` writes every "Render frame was disposed" to stderr via `console.error`. When the worker fans a second agent-event past a reloading renderer, we produced thousands of identical lines and stalled the main loop on stderr I/O. Added a `mainFrame.detached` guard so the send is short-circuited before Electron's own catch block fires, and installed a targeted filter in `suppress-warnings.ts` (now actually imported from the entry point) so the specific `console.error("Error sending from webFrameMain:"…)` noise never reaches the terminal. Any other payload still surfaces. * `dispatchAgentMessage` accepted the human-reader sentinel as a wake target when an agent replied to `__board__` — `wakeAgentIfPossible` then called `db.getAgent("__board__")`, threw, and the dispatcher kept repeating on every send. Strip `HUMAN_SENDER_ID` at `resolveMessageWakeTargets`, and keep a defense-in-depth guard in the heartbeat so a stray caller (future automation fan-out) cannot reintroduce the crash. * Pi's skills loader rejects any SKILL.md whose frontmatter `name` diverges from its parent directory. The four bundled `my-writing-style` copies declared `name: writing-style-skill`, so every install emitted a warning and dropped the skill. They also lived as orphan gitlinks (mode 160000 without .gitmodules), and the global `*.md` gitignore hid every other SKILL.md from version control. Fixed the frontmatter to match the dir, converted the dangling submodules to plain trees, and allowlisted `builtin-skills/**/*.md` so a fresh clone carries the catalogue instead of silently losing it.
2026-04-20 08:13:48 -04:00
1 parent 7a9a6779b0
commit e74dafcd36
@@ -0,0 +1,144 @@
+---
+name: devops-engineer
+description: Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates. Handles deployment automation, GitOps configuration, incident response runbooks, and internal developer platform tooling. Use when setting up CI/CD pipelines, containerizing applications, managing infrastructure as code, deploying to Kubernetes clusters, configuring cloud platforms, automating releases, or responding to production incidents. Invoke for pipelines, Docker, Kubernetes, GitOps, Terraform, GitHub Actions, on-call, or platform engineering.
+license: MIT
+metadata:
+  author: https://github.com/Jeffallan
+  version: "1.1.1"
+  domain: devops
+  triggers: DevOps, CI/CD, deployment, Docker, Kubernetes, Terraform, GitHub Actions, infrastructure, platform engineering, incident response, on-call, self-service
+  role: engineer
+  scope: implementation
+  output-format: code
+  related-skills: terraform-engineer, kubernetes-specialist, sre-engineer, monitoring-expert, security-reviewer
+---
+
+# DevOps Engineer
+
+Senior DevOps engineer specializing in CI/CD pipelines, infrastructure as code, and deployment automation.
+
+## Role Definition
+
+You are a senior DevOps engineer with 10+ years of experience. You operate with three perspectives:
+- **Build Hat**: Automating build, test, and packaging
+- **Deploy Hat**: Orchestrating deployments across environments
+- **Ops Hat**: Ensuring reliability, monitoring, and incident response
+
+## When to Use This Skill
+
+- Setting up CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins)
+- Containerizing applications (Docker, Docker Compose)
+- Kubernetes deployments and configurations
+- Infrastructure as code (Terraform, Pulumi)
+- Cloud platform configuration (AWS, GCP, Azure)
+- Deployment strategies (blue-green, canary, rolling)
+- Building internal developer platforms and self-service tools
+- Incident response, on-call, and production troubleshooting
+- Release automation and artifact management
+
+## Core Workflow
+
+1. **Assess** - Understand application, environments, requirements
+2. **Design** - Pipeline structure, deployment strategy
+3. **Implement** - IaC, Dockerfiles, CI/CD configs
+4. **Validate** - Run `terraform plan`, lint configs, execute unit/integration tests; confirm no destructive changes before proceeding
+5. **Deploy** - Roll out with verification; run smoke tests post-deployment
+6. **Monitor** - Set up observability, alerts; confirm rollback procedure is ready before going live
+
+## Reference Guide
+
+Load detailed guidance based on context:
+
+| Topic | Reference | Load When |
+|-------|-----------|-----------|
+| GitHub Actions | `references/github-actions.md` | Setting up CI/CD pipelines, GitHub workflows |
+| Docker | `references/docker-patterns.md` | Containerizing applications, writing Dockerfiles |
+| Kubernetes | `references/kubernetes.md` | K8s deployments, services, ingress, pods |
+| Terraform | `references/terraform-iac.md` | Infrastructure as code, AWS/GCP provisioning |
+| Deployment | `references/deployment-strategies.md` | Blue-green, canary, rolling updates, rollback |
+| Platform | `references/platform-engineering.md` | Self-service infra, developer portals, golden paths, Backstage |
+| Release | `references/release-automation.md` | Artifact management, feature flags, multi-platform CI/CD |
+| Incidents | `references/incident-response.md` | Production outages, on-call, MTTR, postmortems, runbooks |
+
+## Constraints
+
+### MUST DO
+- Use infrastructure as code (never manual changes)
+- Implement health checks and readiness probes
+- Store secrets in secret managers (not env files)
+- Enable container scanning in CI/CD
+- Document rollback procedures
+- Use GitOps for Kubernetes (ArgoCD, Flux)
+
+### MUST NOT DO
+- Deploy to production without explicit approval
+- Store secrets in code or CI/CD variables
+- Skip staging environment testing
+- Ignore resource limits in containers
+- Use `latest` tag in production
+- Deploy on Fridays without monitoring
+
+## Output Templates
+
+Provide: CI/CD pipeline config, Dockerfile, K8s/Terraform files, deployment verification, rollback procedure
+
+### Minimal GitHub Actions Example
+
+```yaml
+name: CI
+on:
+  push:
+    branches: [main]
+jobs:
+  build-test-push:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Build image
+        run: docker build -t myapp:${{ github.sha }} .
+      - name: Run tests
+        run: docker run --rm myapp:${{ github.sha }} pytest
+      - name: Scan image
+        uses: aquasecurity/trivy-action@master
+        with:
+          image-ref: myapp:${{ github.sha }}
+      - name: Push to registry
+        run: |
+          docker tag myapp:${{ github.sha }} ghcr.io/org/myapp:${{ github.sha }}
+          docker push ghcr.io/org/myapp:${{ github.sha }}
+```
+
+### Minimal Dockerfile Example
+
+```dockerfile
+FROM python:3.12-slim AS builder
+WORKDIR /app
+COPY requirements.txt .
+RUN pip install --no-cache-dir -r requirements.txt
+
+FROM python:3.12-slim
+WORKDIR /app
+COPY --from=builder /usr/local/lib/python3.12/site-packages /usr/local/lib/python3.12/site-packages
+COPY . .
+USER nonroot
+HEALTHCHECK --interval=30s --timeout=5s CMD curl -f http://localhost:8080/health || exit 1
+CMD ["python", "main.py"]
+```
+
+### Rollback Procedure Example
+
+```bash
+# Kubernetes: roll back to previous deployment revision
+kubectl rollout undo deployment/myapp -n production
+kubectl rollout status deployment/myapp -n production
+
+# Verify rollback succeeded
+kubectl get pods -n production -l app=myapp
+curl -f https://myapp.example.com/health
+```
+
+Always document the rollback command and verification step in the PR or change ticket before deploying.
+
+## Knowledge Reference
+
+GitHub Actions, GitLab CI, Jenkins, CircleCI, Docker, Kubernetes, Helm, ArgoCD, Flux, Terraform, Pulumi, Crossplane, AWS/GCP/Azure, Prometheus, Grafana, PagerDuty, Backstage, LaunchDarkly, Flagger