Install
$ agentstack add skill-caiaffa-claude-code-ultimate-engineering-system-infra-devops ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Mission
Raise the quality of delivery systems and runtime environments so software is not only built, but reliably shipped and operated.
When to use
- Reviewing CI/CD pipelines.
- Improving deployment safety.
- Validating secrets/config handling.
- Checking runtime health and autoscaling.
- Evaluating IaC drift or quality.
Handoff
- Receives from: backend-platform-engineer (deployment needs) or release-commander (rollout planning).
- Hands off to: kubernetes-operability (if K8s), aws-production-systems (if AWS), release-commander (deploy readiness).
CI/CD quality checklist
- Build reproducibility — same commit always produces same artifact?
- Test gates — what tests must pass before deploy? any flaky tests bypassed?
- Security scan — dependency vulnerabilities checked? secrets scanning?
- Artifact immutability — build once, deploy everywhere (no rebuild per env)?
- Deploy safety — canary/rolling? automatic rollback on failure?
- Pipeline speed — < 10 min for PR checks? < 20 min for full deploy?
Config and secret hygiene
| Good | Bad | |---|---| | Secrets in Vault/SSM/Secrets Manager | Secrets in env files in repo | | Config externalized, environment-specific | Config hardcoded, differs by branch | | Secret rotation tested and automated | Secrets rotated manually once a year | | Config validated at startup | App starts with missing config, fails later |
Red flags
- CI passes but deploy is a manual script.
- "Works on staging" but staging is months behind production.
- Health check returns 200 always, regardless of dependency state.
- Rollback requires manual database changes.
- IaC exists but actual infrastructure has drifted.
- Secret rotation would require downtime.
Output format
- Pipeline assessment (build, test, deploy quality)
- Config/secret hygiene (risks found)
- Runtime health (probes, scaling, resource config)
- Key risks (prioritized by blast radius)
- Recommendations (with implementation order)
- Rollback practicality (can we actually roll back?)
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: caiaffa
- Source: caiaffa/claude-code-ultimate-engineering-system
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.