Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

darwin-rollback

Estrelas7

Forks1

Atualizado11 de junho de 2026 às 13:58

GitOps rollback workflow for crisis recovery. Activates for Mode:rollback tasks or when reverting a deployment via git revert.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

The-Darwin-Project

The-Darwin-Project/Blackboard

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	darwin-rollback
description	GitOps rollback workflow for crisis recovery. Activates for Mode:rollback tasks or when reverting a deployment via git revert.
roles	["sysadmin"]
modes	["execute","rollback"]

Darwin Rollback Workflow

When to Use

You are in rollback mode. FRIDAY has determined that the last change caused a problem and needs to be reverted.

Rollback Steps

Sync with the remote before making changes
Identify the commit to revert by reviewing recent history
Revert exactly one commit (preserve history -- never reset)
Verify the revert by reviewing the diff before pushing
Push the revert to the remote
Report: Confirm the revert was pushed using team_send_results

Rules

ONLY revert the most recent commit. If multiple commits need reverting, stop and report to FRIDAY.
NEVER use git reset -- always use git revert to preserve history.
NEVER force push.
After pushing, report: "Revert committed and pushed. The CD controller will handle the rollout."
Do NOT verify ArgoCD sync yourself -- FRIDAY will trigger verification separately. If asked to check sync status, use your available tools (ArgoCD MCP, K8s MCP, CLI).

What to Report

**Action**: Reverted commit <SHA>
**Repo**: <repo URL>
**Original change**: <what the reverted commit did>
**Verification**: Revert pushed, waiting for CD sync

Mais deste repositório

mesmo repositório

darwin-dockerfile-safety

The-Darwin-Project/Blackboard

Safety rules for modifying Dockerfiles and Containerfiles. Use when editing container build files.

2026-07-217

darwin-reporting-context

The-Darwin-Project/Blackboard

MR/PR context gathering and diagnostic reporting guidelines. Activates when working on events that reference MRs/PRs or when reporting investigation findings.

2026-07-217

darwin-team-huddle

The-Darwin-Project/Blackboard

Team coordination for implement and test modes. Developer and QE use team_send_results for final reports, team_huddle for mid-task questions to FRIDAY.

2026-07-217

darwin-gitops

The-Darwin-Project/Blackboard

GitOps workflow rules for modifying infrastructure via git. Use when cloning repos, modifying Helm values, committing, pushing, or verifying deployments.

2026-07-137

darwin-mr-lifecycle

The-Darwin-Project/Blackboard

MR/PR lifecycle operations -- pipeline check, retest, merge, conflict reporting. Extends darwin-gitlab-ops.

2026-07-137

darwin-comms

The-Darwin-Project/Blackboard

Report findings and status updates to the Darwin FRIDAY. Use team_send_results for final reports (task modes). In message mode, use team_send_message instead.

2026-07-097

name	darwin-rollback
description	GitOps rollback workflow for crisis recovery. Activates for Mode:rollback tasks or when reverting a deployment via git revert.
roles	["sysadmin"]
modes	["execute","rollback"]

Darwin Rollback Workflow

When to Use

You are in rollback mode. FRIDAY has determined that the last change caused a problem and needs to be reverted.

Rollback Steps

Sync with the remote before making changes
Identify the commit to revert by reviewing recent history
Revert exactly one commit (preserve history -- never reset)
Verify the revert by reviewing the diff before pushing
Push the revert to the remote
Report: Confirm the revert was pushed using team_send_results

Rules

ONLY revert the most recent commit. If multiple commits need reverting, stop and report to FRIDAY.
NEVER use git reset -- always use git revert to preserve history.
NEVER force push.
After pushing, report: "Revert committed and pushed. The CD controller will handle the rollout."
Do NOT verify ArgoCD sync yourself -- FRIDAY will trigger verification separately. If asked to check sync status, use your available tools (ArgoCD MCP, K8s MCP, CLI).

What to Report

**Action**: Reverted commit <SHA>
**Repo**: <repo URL>
**Original change**: <what the reverted commit did>
**Verification**: Revert pushed, waiting for CD sync