debug-pipeline

Inspect and diagnose AutoRun pipeline failures via snapshots and audit logs.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/mcleanT/AutoReview --skill debug-pipeline-mcleant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-pipeline
Source: https://github.com/mcleanT/AutoReview/tree/main/.claude/skills/debug-pipeline
Command: npx skills add https://github.com/mcleanT/AutoReview --skill debug-pipeline-mcleant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides step-by-step guidance and commands to inspect, diagnose, and recover AutoReview pipeline failures by loading snapshots, examining node state and audit logs, identifying common errors, and resuming execution from the last good state.

Core Features & Use Cases

  • Snapshot inspection: Load and summarize KnowledgeBase snapshots to see current_phase, candidate counts, extractions, and token usage.
  • Node diagnosis: Review the audit log, token consumption, and common failure modes for all 15 DAG nodes and map failures to fixes.
  • Resume procedures: Clear instructions for resuming runs from a specific node via the CLI or Python API, plus guidance on config fixes (API keys, token budgets).
  • Use Case: When a run hits TokenBudgetExceeded during section_writing or a search API fails, use this skill to find the failing node, apply the appropriate fix, and restart the pipeline from the proper snapshot.

Quick Start

Load the latest snapshot at output/snapshots/latest.json, inspect phase, candidate and extraction counts, check the last audit log entries, apply fixes, and resume from the failing or chosen node.

Frequently Asked Questions about debug-pipeline

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

FAQPage Schema
How do I troubleshoot an AutoReview pipeline failure from a snapshot?

To troubleshoot an AutoReview pipeline failure, load the latest KnowledgeBase snapshot at output/snapshots/latest.json, inspect the current_phase and candidate counts, and review node audit logs to identify errors to pinpoint the failing DAG node.

What is the best way to resume a failed LLM pipeline run after a token budget error?

The best way to resume an LLM pipeline run after a TokenBudgetExceeded error is to load the last good snapshot, adjust the token budget configuration, and restart execution from the failing node via the CLI or Python API.

Can I diagnose DAG node failures using audit logs and token usage data?

Yes, you can diagnose DAG node failures by reviewing audit logs and analyzing token consumption across all 15 nodes to map common failure modes like API errors to their specific fixes.

Do I need configured LLM and service API keys to resume pipeline execution from a specific node?

Yes, you need configured LLM and service API keys to resume pipeline execution and re-run downstream nodes, alongside access to output/snapshot files and the KnowledgeBase load_snapshot/save_snapshot APIs.

Why does my pipeline fail during section_writing and how can I recover the run?

Your pipeline may fail during section_writing due to a TokenBudgetExceeded error or search API failure; recover the run by loading the previous snapshot, applying config fixes, and resuming from that node.