pipeline-resume

Validate pipeline-state files and resume interrupted pipelines at the correct phase.

1|Updated Mar 15, 2026

Search Tags:#automation #orchestration #resume #pipeline #git-workflow #state-validation #pipeline-state

Ready to run

npx skills add https://github.com/paulingham/.claude --skill pipeline-resume-paulingham

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pipeline-resume
Source: https://github.com/paulingham/.claude/tree/main/skills/pipeline-resume
Command: npx skills add https://github.com/paulingham/.claude --skill pipeline-resume-paulingham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resuming an in-progress pipeline reliably after interruptions by validating the saved state and re-entering at the correct phase.

Core Features & Use Cases

Validate state schema and determine current phase from pipeline-state files.
Determine resume point and re-enter the pipeline, skipping completed phases.
Verify repository state (branch, working tree) before continuing, and emit resumed metadata.
Use in scenarios where a pipeline was interrupted by context compaction, session end, or agent failure.

Quick Start

Resume a stalled pipeline by selecting the active pipeline and continuing from the next pending phase.

Frequently Asked Questions about pipeline-resume

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

FAQPage Schema

How do I resume a pipeline after a session ends or agent failure?▼

To resume a pipeline after an interruption, the system validates saved pipeline-state files, determines the current phase, and re-enters the pipeline at the correct pending step. It skips completed phases and updates the state metadata.

What is pipeline state validation and when do I need it?▼

Pipeline state validation is the process of enforcing a YAML frontmatter schema on state files to determine the next pending phase. You need it when an in-progress workflow is interrupted by context compaction or agent failure and must continue accurately.

How do I verify git branch integrity before continuing an orchestration workflow?▼

Git branch integrity is verified by checking the repository state, including the current branch and working tree, before continuing the pipeline. This ensures the environment matches the saved state before re-entering the workflow.

Can I use pipeline-state files to skip completed automation phases?▼

Yes, pipeline-state files allow the orchestration harness to skip completed phases. The system detects the next pending phase from the YAML frontmatter and re-enters the pipeline exactly at that point.

What is the best way to recover a stalled git-workflow pipeline?▼

The best way to recover a stalled git-workflow pipeline is to select the active pipeline and trigger the harness pipeline. The system validates the state schema, verifies repository state, and continues from the appropriate phase.

Does pipeline-resume work without YAML frontmatter in state files?▼

No, pipeline-resume enforces a YAML frontmatter schema for state files to detect the current phase and resume point. Without this schema, the system cannot validate the pipeline state or determine where to re-enter the workflow.