spawn-builder

Coordinate builder-agent to run build and test tasks after coder-agent changes.

Updated Dec 25, 2025
One-click install
npx skills add https://github.com/Zeliper/z-coder --skill spawn-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spawn-builder
Source: https://github.com/Zeliper/z-coder/tree/main/.claude/skills/spawn-builder
Command: npx skills add https://github.com/Zeliper/z-coder --skill spawn-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures code builds and tests are executed after coding changes, providing early feedback and reducing manual debugging.

Core Features & Use Cases

  • Post-Coding Build/Test: Spawn builder-agent after coder-agent completes.
  • CI-Quality Assurance: Report build and test outcomes with clear status.
  • Recovery Guidance: Offer rerun paths when failures occur.

Quick Start

After coder-agent modifications, spawn-builder for TASK-001 to execute build/test commands and report results.

Frequently Asked Questions about spawn-builder

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

FAQPage Schema
How do I run builds and tests automatically after code changes?

spawn-builder coordinates a builder-agent to execute builds and tests after coder-agent modifications complete. It applies the Task tool to enforce standardized execution, reports results with clear statuses (COMPLETED, FAILED, PENDING_INPUT), and provides retry guidance when failures occur.

What's the best way to verify code changes in a CI pipeline?

Spawn builder-agent after coding tasks to run build and test commands with CI-quality assurance. The Skill reports outcomes with error details and standardized status tracking, enabling early feedback and reducing manual debugging cycles.

Can I automate build verification when my coder-agent finishes?

Yes. spawn-builder triggers after coder-agent tasks complete, executing builds and tests via builder-agent. It requires explicit prompt structure and file references, then outputs results with statuses and error details for recovery guidance.

How do I handle build and test failures during automation?

spawn-builder enforces standardized error reporting and includes a retry policy for failures. When tests fail or builds error, the Skill outputs detailed error analysis and offers rerun paths to guide recovery without manual intervention.

Do I need manual intervention to run tests after code modifications?

No. spawn-builder removes manual steps by automatically spawning builder-agent to perform builds and tests when code changes require verification. It coordinates the entire workflow and reports outcomes with clear status indicators.

What happens if my build fails during automated testing?

The Skill reports the failure with FAILED status, includes error details for analysis, and provides retry paths. This structured feedback helps identify root causes without rerunning the entire automation workflow manually.