lev-builder

Orchestrate POC-to-production code migration with graph plans and filesystem patches.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/lev-os/lev-content --skill lev-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lev-builder
Source: https://github.com/lev-os/lev-content/tree/main/sources/skills/lev-builder
Command: npx skills add https://github.com/lev-os/lev-content --skill lev-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of developing new features and migrating proof-of-concepts into the main Leviathan codebase, preventing duplicated effort and ensuring code is placed correctly.

Core Features & Use Cases

  • Code Assessment: Analyzes existing code and documentation to identify prior art.
  • Placement Decisioning: Helps determine the correct location for new modules within the Leviathan project structure.
  • Automated Patching: Generates and applies filesystem patches for code migration.
  • End-to-End Validation: Ensures migrated code passes tests and type checks.
  • Use Case: When a developer has a working proof-of-concept for a new authorization module, they can use this Skill to check if similar functionality already exists, decide where it should live in ~/lev/core, apply the necessary code changes, and validate its integration.

Quick Start

Use the lev-builder skill to assess the existing code for 'fleet authorization' and determine its placement.

Frequently Asked Questions about lev-builder

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

FAQPage Schema
How do I migrate proof-of-concept code to a core production path?

To migrate proof-of-concept code to a core production path, this Skill assesses existing codebases, performs prior art checks, and generates filesystem patches to apply changes correctly. It orchestrates the entire workflow to ensure proper code placement within the ecosystem.

What is a prior art check in developer workflow code migration?

A prior art check in code migration analyzes existing code and documentation to identify similar functionality, preventing duplicated effort. This ensures new modules are not recreating features that already exist before proceeding with development.

How do I determine the correct code placement for a new module?

To determine the correct code placement for a new module, this Skill evaluates the project structure and generates graph plans to guide placement decisions. It helps developers identify the exact location within the core codebase where new features should reside.

Does code migration validate end-to-end functionality before moving to core paths?

Yes, code migration validates end-to-end functionality before moving to core paths. This Skill ensures that migrated proof-of-concepts pass required tests and type checks, confirming full integration before the code is finalized in the main codebase.

Can I automate filesystem patches when moving code to the main codebase?

Yes, you can automate filesystem patches when moving code to the main codebase. This Skill generates and applies the necessary filesystem patches automatically, streamlining the migration process from proof-of-concept into the core project structure.