add-pipeline-node

Scaffold and wire a new DAG node into the AutoReview pipeline.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Step-by-step checklist for adding a new DAG node to the AutoReview pipeline. This guide helps engineers create a self-contained, properly wired node with templates for prompts, tests, and DAG integration, ensuring consistency and auditability across the pipeline.

Core Features & Use Cases

  • Step-by-step scaffolding for a new DAG node, including prompt templates, node logic, tests, and DAG wiring.
  • End-to-end integration guidance covering configuration, auditing, and token-budgeting to maintain pipeline discipline.
  • Use Case: Extend the AutoReview pipeline with a new analysis or processing stage without impacting existing nodes, while preserving observability and reliability.

Quick Start

Follow the step-by-step checklist in this skill to scaffold and wire a new DAG node into the AutoReview pipeline.

Frequently Asked Questions about add-pipeline-node

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

FAQPage Schema
How do I add a new DAG node to an existing pipeline?

Adding a new DAG node to a pipeline requires a modular approach that covers prompt creation, node logic, tests, and DAG wiring. This ensures the new processing stage integrates safely without impacting existing nodes.

What is the process for extending an automated review pipeline with new analysis stages?

Extending an automated review pipeline involves scaffolding a self-contained DAG node and wiring it into the existing workflow. This ensures new analysis stages maintain pipeline discipline through token budgeting and compatibility checks.

How do I ensure pipeline consistency when adding a new processing node?

Pipeline consistency is maintained by applying token budgeting, audits, and compatibility checks across the new DAG node and downstream components. Standardized templates for prompts and tests further enforce this discipline.

Do I need to write tests when adding a new DAG node to the pipeline?

Yes, writing tests is required when adding a new DAG node to the pipeline. The integration process includes templates specifically for tests to ensure the new processing stage is self-contained and does not break existing workflows.

What should I check before wiring a new node into a DAG workflow?

Before wiring a new node into a DAG workflow, you should perform compatibility checks across downstream nodes and audit token budgets. This prevents the new processing stage from negatively impacting existing pipeline operations.