pipeline-resume

Resume failed PCB pipelines from the last successful checkpoint.

2|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/pjcau/esp32-emu-turbo --skill pipeline-resume
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pipeline-resume
Source: https://github.com/pjcau/esp32-emu-turbo/tree/main/.claude/skills/pipeline-resume
Command: npx skills add https://github.com/pjcau/esp32-emu-turbo --skill pipeline-resume

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill helps developers continue a failed PCB production preparation pipeline without rerunning earlier steps, saving time and resources.

Core Features & Use Cases

  • Checkpoint reading: Detects the last successful pipeline step from a JSON file.
  • Selective resumption: Executes only remaining steps, updating checkpoints after each success.
  • SHA validation: Ensures the PCB design hasn't changed before resuming.
  • Use case: When a PCB generation or verification step fails, invoke this skill to pick up from the next step instead of restarting the whole process.

Quick Start

Ask the skill to resume the PCB preparation pipeline from the last checkpoint.

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 failed PCB pipeline from the last successful checkpoint?

To resume a failed PCB pipeline, the skill reads the pipeline-checkpoint.json file to detect the last successful step and executes only the remaining generation, zone filling, or verification steps. It updates the checkpoint file after each successful step.

Does the pipeline resume process verify that the KiCad PCB design hasn't changed?

Yes, the pipeline resume process performs SHA validation on the .kicad_pcb design file. This ensures the PCB design hasn't changed before resuming, preventing inconsistencies between the checkpoint state and the current design file.

What files and permissions do I need to resume an ESP32 PCB generation pipeline?

Resuming an ESP32 PCB generation pipeline requires access to the pipeline-checkpoint.json file and the .kicad_pcb design file. You also need execution permissions for Bash, Python, and Docker commands to run the remaining steps.

Can I bypass completed DFM and DFA verification steps when restarting a PCB production pipeline?

Yes, you can bypass completed DFM and DFA verification steps. The skill selectively resumes the PCB production pipeline by reading the last successful checkpoint and continuing from the appropriate step, skipping all previously completed stages.

Why does my PCB pipeline restart from the beginning instead of resuming from the gerber export step?

A PCB pipeline restarts from the beginning if the checkpoint reading fails or the SHA validation detects changes in the .kicad_pcb file. The pipeline-checkpoint.json file must accurately reflect the last successful state to resume correctly.