om-auto-continue-pr

Resume paused auto-create-pr runs from the first unchecked Progress step.

6|2|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/SHGrowth/om-superpowers --skill om-auto-continue-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: om-auto-continue-pr
Source: https://github.com/SHGrowth/om-superpowers/tree/main/skills/om-auto-continue-pr
Command: npx skills add https://github.com/SHGrowth/om-superpowers --skill om-auto-continue-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates resuming in-progress auto-create-pr runs by re-entering the same worktree, locating the linked execution plan, and resuming from the first unchecked Progress step.

Core Features & Use Cases

  • Resume paused auto-create-pr runs: Re-enter the same worktree without disrupting the main workflow and continue from the first pending step.
  • Locking discipline & environment isolation: Enforce in-progress lock checks, use isolated temporary worktrees, and perform safe teardown after completion.
  • Plan parsing & resume control: Locate the plan path from the PR body, support --from overrides, and drive the PR to completion with the same validation gates as the initial run.

Quick Start

Call the skill with /auto-continue-pr <PR-number> to resume an in-progress PR, optionally using --from to choose a resume point or --force to override ownership.

Frequently Asked Questions about om-auto-continue-pr

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

FAQPage Schema
How do I resume an in-progress pull request from a failed step?▼

To resume an in-progress pull request, you can use an auto-continue-pr run to re-enter the linked git-worktree and continue from the first unchecked progress step. It preserves the original lock discipline and validation gates until completion.

Can I restart a paused PR creation run without losing the original environment isolation?▼

Yes, resuming a paused PR creation run re-enters the same isolated temporary worktree to preserve environment isolation. It enforces in-progress lock checks and performs safe teardown after applying phase-by-phase updates.

What is the best way to override a PR resume point and force ownership?▼

The best way to override a PR resume point or force ownership is by using optional --from and --force options. This allows you to choose a specific resume point and override ownership while driving the PR to completion.

How does plan parsing work when continuing an automated PR workflow?▼

Plan parsing works by locating the plan path directly from the PR body to resume an automated PR workflow. It reads the PR tracking plan to apply phase-by-phase updates safely within the isolated worktree.

Do I need to manually locate the execution plan to resume a pull request?▼

No, you do not need to manually locate the execution plan to resume a pull request. The automation reads the PR body to locate the linked execution plan and automatically continues from the first pending step.

Why does resuming a pull request require lock discipline and validation gates?▼

Resuming a pull request requires lock discipline and validation gates to ensure safe teardown and prevent workflow disruption. It enforces in-progress lock checks to maintain environment isolation during phase-by-phase updates.