agentleFS
Sign inStart free
pilotmainpilotmain/AethOS/skills/rollback-deploy/SKILL.md

rollback-deploy

Skill1 starsChanged 4 months agoApache-2.0View on GitHub

Roll a service back to a previous known-good deployment, governed.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a governed rollback preflight targeting that deployment/commit (blast radius + that this replaces the current running version).

    line 16
  2. Distinctive:

    After execution, verify the rolled-back version is live and healthy from fresh evidence (commit + post-rollback health/logs).

    line 19
  3. Distinctive:

    create rollback preflight (governed)

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

When to use

A deploy made things worse and the operator wants to revert ("rollback aethos-api to the last working deploy").

Steps

  1. Resolve provider + project + environment + service.
  2. List recent deployments and identify the last known-good one (status SUCCESS, healthy, prior commit). Show the operator the candidate before acting.
  3. Create a governed rollback preflight targeting that deployment/commit (blast radius + that this replaces the current running version). Do NOT execute.
  4. Operator approves.
  5. After execution, verify the rolled-back version is live and healthy from fresh evidence (commit + post-rollback health/logs).

Mutation tools

  • create rollback preflight (governed)
  • verify_deployment (post-approval)

Governance

Mutation. Preflight → approve → execute → verify. Confirm the rollback target with the operator before creating the preflight.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free