extract-skill
Reverse-engineer design systems, tokens, and components from live products or screenshots
Roll back to a previous checkpoint via git — use when a change went wrong and you need to revert
$ npx -y skills add nyldn/claude-octopus --skill skill-rollback --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/skill-rollbackContext preview
The summary Claude sees to decide when to auto-load this skill.
Roll back to a previous checkpoint via git — use when a change went wrong and you need to revert
name: skill-rollback description: "Roll back to a previous checkpoint via git — use when a change went wrong and you need to revert" disable-model-invocation: true
> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex. > Cross-reference commands use installed skill names in Codex rather than `/octo:*` slash commands. > Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it. > For host tool equivalents, see `skills/blocks/codex-host-adapter.md`.
Safely rollback to a previous checkpoint while preserving lessons learned.
**Core principle:** List checkpoints → Confirm explicitly → Create safety backup → Restore → Preserve lessons.
Parse the user's request to determine mode:
| User Request | Mode | Action | |--------------|------|--------| | `list`, `show checkpoints`, no argument | LIST | Show available checkpoints | | `octo-checkpoint-*` tag name | ROLLBACK | Rollback to specific checkpoint |
# List all octo checkpoints with dates git tag -l "octo-checkpoint-*" --sort=-creatordate --format='%(refname:short)|%(creatordate:short)|%(contents:subject)'
## Available Checkpoints | Tag | Created | Description | |-----|---------|-------------| | octo-checkpoint-post-discover-20260203-143022 | 2026-02-03 | After Discover phase | | octo-checkpoint-post-define-20260203-150145 | 2026-02-03 | After Define phase | Usage: `/octo:rollback <tag-name>`
**If no checkpoints found:**
No checkpoints found. Checkpoints are created automatically after each Octopus phase. To create a manual checkpoint: git tag -a octo-checkpoint-manual-$(date +%Y%m%d-%H%M%S) -m "Manual checkpoint"
# Check if tag exists git tag -l "$CHECKPOINT_TAG" | grep -q . || echo "TAG_NOT_FOUND"
**If tag not found:**
Checkpoint '$CHECKPOINT_TAG' not found. Available checkpoints: [show list output]
**STOP. Do not proceed.**
# Get list of files that will be changed git diff --name-status HEAD $CHECKPOINT_TAG
Present clearly:
## Rollback Preview **Rolling back to:** `octo-checkpoint-post-discover-20260203-143022` **Created:** 2026-02-03 14:30:22 **Description:** After Discover phase ### Files That Will Be Changed | Status | File | |--------|------| | M | src/auth/login.ts | | D | src/auth/oauth.ts | | A | src/legacy/old-auth.ts | Legend: M=Modified, D=Deleted, A=Added (relative to current state) ### Protected Files (Will NOT be changed) - `.octo/LESSONS.md` - Lessons are always preserved
To confirm this rollback, type ROLLBACK exactly. Any other input will cancel.
**Wait for exact confirmation: `ROLLBACK`**
**CRITICAL:** Do NOT proceed without explicit "ROLLBACK" confirmation.
Before any rollback, create a pre-rollback checkpoint:
# Generate timestamp TIMESTAMP=$(date +%Y%m%d-%H%M%S) # Create safety checkpoint git tag -a "octo-checkpoint-pre-rollback-$TIMESTAMP" -m "Safety checkpoint before rollback to $CHECKPOINT_TAG"
Report:
Created safety checkpoint: octo-checkpoint-pre-rollback-$TIMESTAMP You can return to current state with: /octo:rollback octo-checkpoint-pre-rollback-$TIMESTAMP
# Save current LESSONS.md if it exists if [ -f ".octo/LESSONS.md" ]; then cp .octo/LESSONS.md /tmp/LESSONS_PRESERVED.md LESSONS_PRESERVED=true fi
# Restore files from checkpoint (does NOT move HEAD) git checkout $CHECKPOINT_TAG -- . # Restore preserved LESSONS.md if [ "$LESSONS_PRESERVED" = "true" ]; then cp /tmp/LESSONS_PRESERVED.md .octo/LESSONS.md fi
**Important:** This uses `git checkout <tag> -- .` which:
if [ -f ".octo/STATE.md" ]; then # Append rollback entry to history echo "" >> .octo/STATE.md echo "## Rollback - $(date '+%Y-%m-%d %H:%M')" >> .octo/STATE.md echo "" >> .octo/STATE.md echo "- **Target:** $CHECKPOINT_TAG" >> .octo/STATE.md echo "- **Safety checkpoint:** octo-checkpoint-pre-rollback-$TIMESTAMP" >> .octo/STATE.md echo "- **Reason:** User requested rollback" >> .octo/STATE.md fi
Rollback Complete **Restored to:** `$CHECKPOINT_TAG` **Files restored:** N files **LESSONS.md:** Preserved (not rolled back) **Safety checkpoint created:** `octo-checkpoint-pre-rollback-$TIMESTAMP` ### Next Steps 1. Review the restored files 2. Commit the rollback if satisfied: ```bash git add -A && git commit -m "chore: rollback to $CHECKPOINT_TAG"
3. Or return to previous state:
/octo:rollback octo-checkpoint-pre-rollback-$TIMESTAMP
## Safety Measures | Measure | Implementation | |---------|----------------| | **Always create safety checkpoint** | Pre-rollback tag created BEFORE any file changes | | **Preserve LESSONS.md** | Copy before rollback, restore after | | **Require explicit confirmation** | Must type "ROLLBACK" exactly | | **Show affected files first** | Preview before confirmation | | **No history modification** | Uses checkout, not reset | ## Red Flags - Never Do | Action | Why It's Dangerous | |--------|-------------------| | Rollback without confirmation | Loses work unexpectedly | | Skip safety checkpoint | No recovery path | | Rollback LESSONS.md | Loses accumulated knowledge | | Use `git reset --hard` | Destroys commit history | | For
Every AI model has blind spots. Claude Octopus supports twelve external provider integrations — Codex, Antigravity CLI, Copilot, Qwen, Ollama, Perplexity, OpenRouter, OrcaRouter, OpenCode, Cursor CLI, Grok, and Kimi Code — alongside the built-in Claude Code
Repo: nyldn/claude-octopus
Reverse-engineer design systems, tokens, and components from live products or screenshots
Multi-AI requirements scoping using available external providers (Double Diamond Define phase). Priority triggers: octo define, octo scope, co-define,…
Multi-AI validation, scoring, and review using available external providers (Double Diamond Deliver phase)
Multi-AI implementation using available external providers (Double Diamond Develop phase). DO NOT use for simple code edits, reading/reviewing code, built-in…
Multi-AI research using available external providers (Double Diamond Discover phase)
Decompose and execute large changes, migrations, or multi-issue fixes in parallel with quality gates