baml-iteration

Automate the BAML schema edit, validate, and test loop.

1|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/89jobrien/dotfiles --skill baml-iteration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: baml-iteration
Source: https://github.com/89jobrien/dotfiles/tree/main/dot-claude/skills/baml-iteration
Command: npx skills add https://github.com/89jobrien/dotfiles --skill baml-iteration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Editing BAML schemas in devloop projects can easily drift when changes are large or frequent; this Skill provides a structured loop to edit, validate, test, and regenerate to maintain parity with tooling and prevent integration issues.

Core Features & Use Cases

  • Edit BAML schemas in crates/baml/baml_src/ with parity checks and regeneration guidance.
  • Validate updated schemas against existing clients and generation configurations to ensure compatibility.
  • Run end-to-end tests and analysis to verify the impact of changes before publishing.

Quick Start

Edit BAML schemas in crates/baml/baml_src/ and run the iteration loop to validate changes and trigger regeneration as needed.

Frequently Asked Questions about baml-iteration

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

FAQPage Schema
How do I validate BAML schema changes before regenerating clients?

To validate BAML schema changes, run an end-to-end loop that edits schemas in crates/baml/baml_src/, checks version parity, and verifies compatibility against existing generation configurations before triggering regeneration.

What is the BAML edit, validate, and test loop for devloop projects?

The BAML iteration loop is a structured workflow that applies schema edits, enforces version parity checks, triggers regeneration, and runs analysis to verify changes and prevent integration drift in devloop projects.

How do I prevent schema drift when editing BAML files frequently?

To prevent schema drift when editing BAML files frequently, use a structured iteration loop that validates updated schemas against existing clients and runs end-to-end tests to maintain parity with tooling.

Can I run end-to-end tests on updated BAML schemas to check client compatibility?

Yes, you can run end-to-end tests and analysis on updated BAML schemas to verify the impact of changes and ensure compatibility with existing clients and generation configurations before publishing.

Does BAML schema editing require version parity checks and regeneration?

Yes, BAML schema editing requires version parity checks and regeneration steps to ensure updated schemas maintain compatibility with tooling and prevent integration issues within the devloop project.