How do I install the Rollback Team skill?

Run npx skillmds@latest add vamfi/rollback-team in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Rollback Team safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Rollback Team?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Rollback Team free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Rollback Team?

VAMFI (@vamfi) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Rollback Team by vamfi — Agent Skill

Name: Rollback Team
Author: VAMFI

Rollback Team

Inspect and safely revert a selected Codesemble project transaction while refusing to overwrite later user changes. Use when a user asks to undo, revert, uninstall, or roll back a generated Codex team or project concurrency change.

VAMFI 77799c4 2 files · 3.1 KB Updated Sep 17, 2026

File contents

Roll back a Codex team transaction

Resolve this skill's installed directory and plugin root as ../... Use the absolute bundled CLI path:

node <plugin-root>/scripts/codsemble.mjs

Stop if the script, manifest, or transaction history is missing. Never invent rollback ownership from filenames.

Guardrails

Roll back only Codesemble-owned paths and managed sections listed in the selected transaction.
Never edit global ~/.codex/config.toml, project trust, managed policy, credentials, providers, third-party components, or external systems.
Never overwrite a file whose current hash differs from the recorded transaction postimage.
Do not treat “uninstall the plugin” as permission to delete generated project files or transaction history.
Keep role removal separate from worker-ceiling restoration. Restore the prior project value only if the selected transaction changed it.

Workflow

Run:
```
node <plugin-root>/scripts/codsemble.mjs doctor --workspace <absolute-workspace>
```
Identify available transaction ids, drift, and conflicts. Stop if an incomplete mutation lock or pending record exists. Preserve the target, quarantine, backup, and pending record for manual recovery.
Ask the user to select an exact transaction if the request is ambiguous. Resolve the selected transaction record inside .codex/codsemble/transactions/. Read its metadata and current target hashes without modifying the workspace.
Present a reverse preview:
- transaction id and creation time;
- files that would be restored or removed;
- managed section changes;
- prior and current project concurrency values;
- conflicts caused by later edits;
- what remains untouched.
Never accept a transaction JSON supplied from outside the workspace. The canonical transaction id must resolve inside Codesemble's transaction directory.
Ask for explicit confirmation of the exact transaction id and displayed reverse changes. Do not infer this confirmation from the initial rollback request.

Only after confirmation, run:

node <plugin-root>/scripts/codsemble.mjs rollback \
  --workspace <absolute-workspace> \
  --transaction <exact-transaction-id> \
  --confirm <exact-transaction-id>

If the CLI reports drift or conflict, stop. Provide the conflict details and manual recovery guidance; never force restoration.

Run doctor again. Report what was restored, what conflicted, and whether a fresh Codex session is needed. Explain that rollback does not uninstall the plugin or alter global configuration.

---name: rollback-teamdescription: Inspect and safely revert a selected Codesemble project transaction while refusing to overwrite later user changes. Use when a user asks to undo, revert, uninstall, or roll back a generated Codex team or project concurrency change.---# Roll back a Codex team transactionResolve this skill's installed directory and plugin root as `../..`. Use theabsolute bundled CLI path:```textnode <plugin-root>/scripts/codsemble.mjs```Stop if the script, manifest, or transaction history is missing. Never inventrollback ownership from filenames.## Guardrails- Roll back only Codesemble-owned paths and managed sections listed in the selected transaction.- Never edit global `~/.codex/config.toml`, project trust, managed policy, credentials, providers, third-party components, or external systems.- Never overwrite a file whose current hash differs from the recorded transaction postimage.- Do not treat “uninstall the plugin” as permission to delete generated project files or transaction history.- Keep role removal separate from worker-ceiling restoration. Restore the prior project value only if the selected transaction changed it.## Workflow1. Run: ```text node <plugin-root>/scripts/codsemble.mjs doctor --workspace <absolute-workspace> ``` Identify available transaction ids, drift, and conflicts. Stop if an incomplete mutation lock or pending record exists. Preserve the target, quarantine, backup, and pending record for manual recovery.2. Ask the user to select an exact transaction if the request is ambiguous. Resolve the selected transaction record inside `.codex/codsemble/transactions/`. Read its metadata and current target hashes without modifying the workspace.3. Present a reverse preview: - transaction id and creation time; - files that would be restored or removed; - managed section changes; - prior and current project concurrency values; - conflicts caused by later edits; - what remains untouched. Never accept a transaction JSON supplied from outside the workspace. The canonical transaction id must resolve inside Codesemble's transaction directory.4. Ask for explicit confirmation of the exact transaction id and displayed reverse changes. Do not infer this confirmation from the initial rollback request.5. Only after confirmation, run: ```text node <plugin-root>/scripts/codsemble.mjs rollback \ --workspace <absolute-workspace> \ --transaction <exact-transaction-id> \ --confirm <exact-transaction-id> ``` If the CLI reports drift or conflict, stop. Provide the conflict details and manual recovery guidance; never force restoration.6. Run `doctor` again. Report what was restored, what conflicted, and whether a fresh Codex session is needed. Explain that rollback does not uninstall the plugin or alter global configuration.

Frequently asked questions