agent-builder

Execute approved WORK_PACKETs across repository clones and artifact lanes.

1|Updated Aug 18, 2025
One-click install
npx skills add https://github.com/djb258/imo-creator --skill agent-builder-djb258
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-builder
Source: https://github.com/djb258/imo-creator/tree/main/skills/agent-builder
Command: npx skills add https://github.com/djb258/imo-creator --skill agent-builder-djb258

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the execution of approved work packets, applying code changes, database migrations, and other updates across various repository types, ensuring consistent and controlled deployments.

Core Features & Use Cases

  • Automated Execution: Runs predefined tasks (WORK_PACKETs) against specified code repositories.
  • Multi-Lane Processing: Supports standard code changes, database migrations, UI updates, container builds, and documentation generation.
  • Use Case: After a new feature is planned and a WORK_PACKET is generated, this Skill can automatically clone the target repository, apply the code changes, run database migrations, and build the necessary artifacts, handing off the results for auditing.

Quick Start

Use the agent-builder skill to execute the work packet with ID 'wp-12345' against the 'my-app' repository.

Frequently Asked Questions about agent-builder

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

FAQPage Schema
How do I automate code execution and apply changes across multiple repositories?

You can automate code execution by running approved work packets against mounted child repository clones. This process handles repo resolution, mounting, and execution routing to apply code changes and database migrations across standard, DB, UI, container, and documentation lanes.

What is a work packet in the context of automated repository deployment?

A work packet is a predefined task containing approved code changes, database migrations, or updates. It is executed against specified code repositories to ensure consistent and controlled deployments across various repository types while producing necessary artifacts.

How do I execute database migrations and UI updates as part of a CI/CD pipeline?

You can execute database migrations and UI updates by processing work packets through multi-lane routing. The system clones the target repository, applies the changes, runs migrations, and builds artifacts for auditing and downstream deployment.

Does automated repository execution protect specific paths and assets during deployment?

Yes, automated repository execution enforces strict adherence to allowed paths and protected assets. It includes robust error handling and integrity checks during both the cloning and execution phases to maintain strict repository security.

What happens after a work packet is executed against a target repository?

After execution, the system produces necessary artifacts and hands off the results for auditing. This ensures that all applied code changes, database migrations, and container builds are verified and available for downstream review.