resonance-engineering-devops

Implements CI/CD pipelines, Infrastructure as Code, rollback plans, and environment parity audits.

Updated Dec 1, 2025
One-click install
npx skills add https://github.com/manusco/wolfgang --skill resonance-engineering-devops-manusco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resonance-engineering-devops
Source: https://github.com/manusco/wolfgang/tree/main/.agents/skills/engineering/devops
Command: npx skills add https://github.com/manusco/wolfgang --skill resonance-engineering-devops-manusco

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Deployments fail when pipelines are manual, secrets leak into repositories, staging diverges from production, and no tested rollback path exists. This Skill enforces Infrastructure as Code, automated verification, and incident response discipline so releases stay predictable. ## Core Features & Use Cases - Pipeline Construction: Generates complete CI/CD workflow files (e.g., GitHub Actions) with build, lint, test, and deploy stages gated by job dependencies. - Infrastructure Provisioning: Produces Dockerfile, Terraform, and Fly.io configurations using a platform decision tree that matches workloads to Vercel, Fly.io, Cloud Run, or managed databases. - Incident Response & Rollback: Provides a severity-classified triage sequence that rolls back to the last known good deploy before root cause analysis. - Environment Parity Audits: Detects staging/production drift and proposes automated parity checks in CI. - Use Case: Before go-live, paste your deploy workflow for review; the Skill flags hardcoded secrets, ClickOps changes, and missing rollback paths, then refuses sign-off until each is remediated. ## Quick Start Ask the agent to create a CI/CD pipeline for your project that runs tests and deploys to your hosting platform with a verified rollback path.

Frequently Asked Questions about resonance-engineering-devops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a CI/CD pipeline with GitHub Actions?▼

Define separate jobs for lint, typecheck, test, and deploy, with the deploy job gated by a needs dependency on all test jobs. Reference credentials through GitHub Secrets rather than committing them, and confirm a rollback mechanism such as Vercel instant rollback before merging.

What hosting platform should I use for my web app?▼

Frontend and fullstack JavaScript apps go to Vercel or Netlify, containerized backends go to Fly.io or Google Cloud Run, and databases go to managed services like Neon or Supabase. Never run a database on the same host as the application.

What should I do first when production is down?▼

Roll back to the last known good deploy immediately before investigating. Acknowledge the alert, verify the rollback stabilizes the symptom, then investigate logs in staging and write a root cause analysis. Never debug directly on production.

Why does my app work in staging but break in production?▼

This is an environment parity failure, typically caused by schema, config, or data shape differences between environments. Document the exact gaps, migrate staging to match production, and add an automated parity check to CI instead of writing code workarounds.

How do I reduce Docker image size for Node.js apps?▼

Use multi-stage builds: install dependencies and build in a builder stage, then copy only the compiled output into a slim runtime stage without devDependencies. Order layers so package.json installs cache separately from source changes, and never run the container as root.