بنقرة واحدة
rollback
Revert changes when implementation fails. Use for "rollback", "undo", "revert", "go back", "start over".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Revert changes when implementation fails. Use for "rollback", "undo", "revert", "go back", "start over".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | rollback |
| description | Revert changes when implementation fails. Use for "rollback", "undo", "revert", "go back", "start over". |
| argument-hint | [target] |
| disable-model-invocation | true |
| user-invocable | true |
Safely revert changes when things go wrong.
Ask user:
git status
git log --oneline -10
git diff --stat HEAD~5
Show:
Current State:
- Branch: main
- Uncommitted: 2 files modified
- Recent commits:
abc123 - feat: add form
def456 - fix: validation
...
Rollback to checkpoint start:
git log --oneline --grep="CP2"
Rollback specific commits:
git log --oneline -10
Single file:
git log --oneline -- src/path/file.tsx
Ask: "Any code to save before rolling back?"
If yes:
git branch backup-[date]I will run:
1. git stash (save uncommitted)
2. git reset --hard [commit]
This will discard changes since [target].
Type 'confirm' to proceed.
# Safe methods:
git reset --hard [commit] # Clean reset
git revert [commit]..HEAD # Preserve history
git checkout [commit] -- path/file # Single file
Update .planning/CHECKPOINTS.md:
bun run build
git status
Rollback complete!
Rolled back to: abc123 - feat: setup
Build: Passing
Backup: backup-2026-02-01
| Scenario | Command |
|---|---|
| Undo last commit | git reset --soft HEAD~1 |
| Start checkpoint over | git reset --hard [cp-start] |
| Revert single file | git checkout [commit] -- file |
| Keep some changes | git stash → reset → git stash pop |
git reflog # Find lost commits
git checkout [reflog-hash] # Recover
Executes all tasks in a specific phase using wave-based parallel execution (max 4 agents per wave). Spawns small-coder and high-coder agents based on progress.json complexity. Updates progress.json after EACH wave so completed tasks immediately unblock dependents. Accepts phase number as argument (/execute-phase 3) or asks via AskUserQuestion. Triggers on: execute phase, run phase, build phase, develop phase, start phase.
Generates Vitest test files from test-plan.md using the qa-specialist agent. Reads the test plan and vitest best practices, then spawns qa-specialist agents to produce .test.ts files in the root tests/ directory for features, shared tests, and Supabase integration tests. Tests verify behavior via database operations and RLS policies — no UI testing. Triggers on: generate test, generate tests, create tests, write tests, test generation.
Orchestrates sequential project planning. First validates user intent via AskUserQuestion (MANDATORY), then spawns ui-ux-specialist to create ui-ux-plan.md, then tech-lead-specialist to create dev-plan.md from ui-ux-plan.md, then spawns frontend-specialist and backend-specialist in parallel to create their detailed plans from dev-plan.md, then spawns qa-specialist to create test-plan.md from dev-plan.md and backend-plan.md. Triggers on: plan, create plan, plan project, project plan, full plan, prd to plan.
Runs ALL Vitest tests across /features, /tests, and /supabase directories. Executes tests via npx vitest run, collects results, and generates test.result.json (replaced on every run). Uses qa-specialist to analyze failures and provide actionable feedback. Triggers on: run test all, run all tests, test all, vitest all, run tests.
Runs Vitest tests for a specific phase chosen by the user. Reads test-plan.md to identify phases, asks user which phase to run via AskUserQuestion, executes only those test files, and generates test.result.json (replaced on every run). Uses qa-specialist to analyze failures. Triggers on: run test phase, test phase, run phase test, test specific phase.
Verifies and updates tests after code changes. Detects what changed (git diff, changes.json), compares against test-plan.md, then spawns qa-specialist agents to update test-plan.md and edit/create test files in /features, /tests, /supabase. Use after /developer or manual changes to keep tests in sync. Triggers on: verify test, verify tests, sync tests, update tests, check tests, test verify.