dipeo-codegen-pipeline

Route simple codegen tasks through the DiPeO TypeScript-to-Python/GraphQL pipeline.

12|2|Updated May 29, 2025
One-click install
npx skills add https://github.com/sorryhyun/DiPeO --skill dipeo-codegen-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dipeo-codegen-pipeline
Source: https://github.com/sorryhyun/DiPeO/tree/main/.claude/skills/dipeo-codegen-pipeline
Command: npx skills add https://github.com/sorryhyun/DiPeO --skill dipeo-codegen-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DiPeO's complex code generation pipeline (TypeScript specs → Intermediate Representation → Python/GraphQL) can be daunting to navigate, diagnose, or modify, leading to errors in generated code and slow development. This skill simplifies interaction with the pipeline, providing clear guidance and on-demand documentation.

Core Features & Use Cases

  • Intelligent Task Routing: Quickly determines if a codegen task (e.g., simple spec lookup, workflow questions) can be handled directly by the skill or requires escalation to a specialized agent for complex changes.
  • On-Demand Documentation: Retrieves precise documentation sections for TypeScript model design, IR builder architecture, code generation workflow, and diagnosis procedures using the doc-lookup skill.
  • Diagnosis Guidance: Provides a structured approach to tracing issues from TypeScript specifications through the Intermediate Representation to the final generated Python/GraphQL code, significantly reducing debugging time.
  • Use Case: When a generated GraphQL type is incorrect, this skill can guide you through the diagnosis process, helping you pinpoint whether the issue lies in the TypeScript spec, the IR builder, or the generation template, saving significant debugging time and ensuring accurate code.

Quick Start

Example doc-lookup call for naming standards

python .claude/skills/doc-lookup/scripts/section_search.py
--query "naming-standards"
--paths docs/agents/codegen-pipeline.md
--top 1

Frequently Asked Questions about dipeo-codegen-pipeline

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

FAQPage Schema
How do I debug issues in a TypeScript-to-GraphQL code generation pipeline?

Code generation pipelines route TypeScript specifications through an Intermediate Representation layer to produce GraphQL output. This skill guides you through diagnosis by tracing where errors originate—in the spec, IR builder, or generation template—so you pinpoint the root cause without manual inspection of each stage.

Can I use this skill to fix incorrect generated GraphQL types?

Yes. The skill handles straightforward diagnosis and minor TypeScript spec tweaks to correct generated types. Complex multi-file changes or IR modifications escalate to specialized agents, ensuring simple fixes stay fast while complex work gets expert handling.

What's the workflow for transforming TypeScript specifications into Python and GraphQL code?

The DiPeO pipeline converts TypeScript specs to an Intermediate Representation, then generates Python and GraphQL artifacts. This skill routes your tasks through that pipeline, handles lookups and read-only reviews, and escalates complex changes to maintain pipeline integrity.

How do I look up naming conventions and type mappings for code generation?

The skill retrieves on-demand documentation for TypeScript model design, IR architecture, and naming standards like snake_case conventions. Use doc-lookup queries to find precise guidance without manual documentation searches.

When should I escalate a code generation task instead of handling it directly?

Escalate complex multi-file changes, IR-builder modifications, or tasks beyond straightforward spec tweaks and pattern references. The skill determines fit automatically; if a task exceeds direct handling, it routes to dipeo-codegen-pipeline or dipeo-backend agents.

Does this skill work with TypeScript specs, Python, and GraphQL together?

Yes. The skill operates across the entire DiPeO pipeline supporting TypeScript input, Python and GraphQL outputs, and all intermediate steps. It handles integration workflows, documentation lookups, and diagnosis across all three technologies.