devops-infrastructure

name	devops-infrastructure
description	Manage deployment, Docker, CI/CD, environment, secrets, and infrastructure changes with rollback and verification. Use for operational config or release safety work.

DevOps Infrastructure

Use this skill when the work is about deployment, automation, runtime config, or infrastructure safety rather than application feature code.

Workflow

1. Inspect current infrastructure files and deployment assumptions.
2. Document the desired change and rollback path before editing.
3. Keep secrets out of tracked files and prefer environment-based configuration.
4. If rollout trade-offs, config behavior, or incident context materially affect safety and the user enabled a relevant MCP, load the matching mcp-* skill before editing. If crucial context is unavailable, state the gap and ask before production-affecting actions.
5. Run dry-run commands (for example, terraform plan or docker-compose config) and syntax linters before applying infrastructure changes. If validation fails, fix in-scope config issues first; stop before broader rollout steps if unresolved.
6. Record post-change verification and rollback notes. If no automated rollback is available, state that plainly and get explicit confirmation before destructive or irreversible actions.

Relevant MCP Skills

• mcp-context7 for current tool and platform docs
• mcp-github for workflow, action, and release context
• mcp-sentry for production release and incident validation
• mcp-open-bridge for rollout-option comparison, incident synthesis, and config review

Output

Return:

• Infrastructure goal
• Files changed
• Rollback plan
• Verification run