[rig-claude] Improve Claude dynamic-workflow compatibility for rig - #357
Draft
github-actions[bot] wants to merge 1 commit into
Draft
[rig-claude] Improve Claude dynamic-workflow compatibility for rig#357github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
…ynamic workflows - Update claude-workflow-conversion.md to document rig/globals as the migration path for flat top-level Claude dynamic workflow scripts that use call, pipeline, and parallel outside a body function - Add sample 340-flat-workflow-port.md showing the minimal first-step port using rig/globals ambient proxies, with a pointer to the idiomatic body form as step 2 - Add sample 340 to the Example programs table in the conversion reference Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Compatibility gap addressed
The
claude-workflow-conversion.mdreference described how to portargs,phase,log,parallel,pipeline, andcallinto aworkflow({ body }), but never explained how to do a minimal first-step port for flat Claude dynamic workflow scripts — those whose orchestration code runs at the module top-level using injected globals (call,pipeline,parallel) rather than inside abodyfunction.A developer porting such a script had no clear path to
rig/globals, which provides exactly those ambient proxies.Why this improves transfer from Claude dynamic workflows to rig
Claude dynamic workflows inject
call/pipeline/parallelas globals. The equivalent in rig isrig/globals, but it was only mentioned indynamic-workflows.mdandSKILL.md— not in the conversion reference a migrating developer would consult first.This PR:
Updates
claude-workflow-conversion.mdto documentrig/globalsas the minimal migration path for flat scripts — with a short inline example showing the pattern — and notes thatbodydestructuring is preferred for new programs.Adds sample
340-flat-workflow-port.mdshowing a side-by-side Claude flat workflow → rig minimal port, with an explicit "Step 2" pointer to the fully idiomaticbodyform (310-workflow-audit-verify.md). This closes the missing two-step migration sample.Adds the new sample to the Example programs table in the conversion reference so it's discoverable alongside the other ports.
Files changed
skills/rig/references/claude-workflow-conversion.md— addedrig/globalssection with inline example; added 340 to the example programs tableskills/rig/samples/340-flat-workflow-port.md— new sample showing flat Claude-style port viarig/globalswith pointer to idiomatic formValidation run
All 464 tests passed (1 typecheck test run, 463 skipped).
Remaining intentional differences
None introduced. The behavior differences table in
claude-workflow-conversion.mdis unchanged.