paw-rewind

Rewind a PAW workflow to a previous stage with safeguards and user confirmation.

39|6|Updated Oct 8, 2025
One-click install
npx skills add https://github.com/lossyrob/phased-agent-workflow --skill paw-rewind
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paw-rewind
Source: https://github.com/lossyrob/phased-agent-workflow/tree/main/skills/paw-rewind
Command: npx skills add https://github.com/lossyrob/phased-agent-workflow --skill paw-rewind

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The PAW rewind skill enables safe rollback of a PAW session's workflow to a previous stage or phase, with safeguards and explicit user confirmation to prevent destructive changes.

Core Features & Use Cases

  • Determine rewind targets from natural language (start, spec, planning, phase N).
  • Validate current state and perform safeguards (uncommitted changes, unpushed commits, orphaned PRs).
  • Identify the target commit and perform a git reset upon user confirmation.
  • Provide an actionable preview and optionally close orphaned PRs per PRs strategy.

Quick Start

Use the paw-rewind skill in a PAW session to revert the workflow to an earlier phase. Confirm before any destructive git reset.

Frequently Asked Questions about paw-rewind

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely rewind a PAW workflow to a previous phase without losing uncommitted changes?

To safely rewind a PAW workflow, this skill validates your current state for uncommitted changes, unpushed commits, and orphaned PRs before requiring explicit user confirmation to perform a git reset. It ensures destructive changes are prevented during phase transitions.

What is the best way to revert a planning stage in a development workflow using git reset?

Reverting a planning stage involves the skill identifying the target commit from natural language inputs like 'start', 'spec', or 'planning', then providing an actionable preview before executing the git reset upon your explicit confirmation.

Can I use natural language to specify a rewind target like spec or phase N during PR review?

Yes, you can specify rewind targets using natural language such as start, spec, planning, or phase N. The skill determines the target commit from these inputs during development and PR review workflows.

How does the rewind safeguard handle orphaned PRs when rolling back a workflow stage?

The safeguard handles orphaned PRs by detecting them during validation and optionally closing them per your PRs strategy before the git reset occurs. It provides an actionable preview to manage these PRs safely.

Why does a workflow rewind require explicit confirmation before executing destructive git operations?

Explicit confirmation is required because the rewind performs a git reset, which is a destructive git operation. The safeguard checks for unpushed commits and uncommitted changes to prevent unintended data loss before you approve the reset.

When should I not use an automated workflow rewind for my git repository?

You should avoid automated workflow rewinds when you have uncommitted changes or unpushed commits that you cannot afford to lose. The skill enforces safeguards to prevent destructive changes, but explicit confirmation is always required.