rollback
FeaturedPrepare and rehearse a recovery path for an intended release. Use when rollback is assumed, untested or previously failed; follow the environment authority for any drill.
Install
Quality Score: 90/100
Skill Content
Details
- Author
- suboss87
- Repository
- suboss87/FDEOps
- Created
- 3 months ago
- Last Updated
- yesterday
- Language
- JavaScript
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
id-rollback
The infra-delivery INCIDENT safe-revert PROCEDURE skill (the recurring/incident rollback step) — the PROCEDURE the generic agent runs when a delivered change did NOT land (a NOT-LANDED realization, an escaped defect, bad config) to restore the last-known-good IaC and prove reality matches it again. The shape is git revert -> reconcile -> verify-landed: revert the offending commit via the governed /foundry:revert (restoring the prior authorized IaC — the reused prior authorization, NOT a no-skip bypass; still subject to the merge floor), drive the GitOps controller's idempotent reconcile toward the REVERTED IaC PINNED to the reverted commit's candidate_sha (the merged-HEAD pin, never an arbitrary HEAD), then run the realization read and RECORD the realization observation via the DEDICATED post-deploy producer emit_realization_evidence(*, change_scope, candidate_sha, post_apply_plan_results, argocd_status, artifact) (scripts/foundry_realization.py, DC3 — a real, live producer) — recording {candidate_sha, post_a
ship
Prepare or execute an authorized controlled release with verified checks, recovery and an operating owner. Use when a customer increment is ready for deployment.
rescue
Triage an outage, loss of stakeholder trust or a failing engagement direction. Use for urgent recovery; distinguish diagnosis from authorized production mitigation.