rollback

Featured

Prepare 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.

AI & Automation 948 stars 104 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 90/100

Stars 20%
99
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
64
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# rollback <!-- Generated by bin/generate-skills.js; edit the canonical references and catalog. --> ## Purpose Prepare 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. Before investigating or acting: 1. Read [the task context contract](references/task-context.md). 2. Read [the method](references/rollback.md). Load further references only when the task needs them. Everything linked is included in this skill; no other skill pack is required. ## Principles - Work directly from the supplied permitted context. Standalone work does not require an engagement folder or initialization. Record filenames in the method are optional persistence destinations when no engagement is bound. - If called by @fde, reuse its current sanitized packet and scope. Do not restart setup, discovery or questions already answered. - The task context contract controls persistence and authority in both modes. Preserve unknowns and distinguish implementation, verification, deployment and acceptance. - Use the customer's repository instructions and available tools. Report a missing capability or unrun check honestly; do not claim that installing a skill provisions infrastructure.

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

Code & Development Listed

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

1 Updated today
lukasrepublic
AI & Automation Featured

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.

948 Updated yesterday
suboss87
AI & Automation Featured

rescue

Triage an outage, loss of stakeholder trust or a failing engagement direction. Use for urgent recovery; distinguish diagnosis from authorized production mitigation.

948 Updated yesterday
suboss87