flow: global storage, list command, and dynamic parameters#18
Merged
Conversation
2fcfeef to
e87f81e
Compare
skapoor8
commented
Jul 9, 2026
skapoor8
left a comment
Contributor
Author
There was a problem hiding this comment.
Self-review evaluated against stated intent. 5 comments (2 BLOCKING, 2 CONSIDER, 1 NOTE) on whether the flow actually chains interactive skills. All findings have since been addressed in commit 4d43708 (non-interactive step contract + NEEDS_INPUT escalation, persisted/reloaded flow context, and authoring guidance for per-step inputs and artifact chaining) — comments retained for the record.
- --global stores flows under ~/.codevoyant/flows, reusable across
projects; list enumerates local + global flows (fixes the old
list->status alias)
- dynamic {{parameters}}: bare text binds to {{input}}, --set for named
params, prompt for anything unset; step outputs thread forward as flow
context, persisted so an interrupted flow resumes with it
- chain interactive skills safely: steps run non-interactively and, when
a step can't resolve a decision, escalate one NEEDS_INPUT question to
the user and re-run; authoring guidance for per-step inputs and
producer -> consumer artifact handoff
Reviews judge whether a change delivers its stated purpose, not just whether the code is clean. Add an INTENT ALIGNMENT dimension, checked first: read the PR/MR title and description as the intent, trace the headline use case end-to-end, and flag anything that undercuts it as BLOCKING even when the code is well-formed. The summary leads with an intent verdict.
4d43708 to
5d284fa
Compare
|
🎉 This PR is included in version 1.56.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
Changes
Extends the
flowskill so users can build reusable, parameterized pipelines that combine multiple skills.--global/-gstorage — save flows under~/.codevoyant/flows/(reusable across every project) instead of the local.codevoyant/flows/. Resolution is local-first then global;--globalforces the global copy. Newreferences/flow-dir.mdcentralizes this for all workflows.flow list— enumerate every flow across both scopes with step counts, status, and parameters. Fixes the previously broken/contradictorylistalias (SKILL.mdsaidlist→status,help.mdsaidlist→review; neither listed anything).{{placeholders}}in any step, resolved at run time: bare text after the name binds to{{input}},--set key=valuebinds named params, anything still unset is prompted for once.flow newrecords the parameter set inflow.md.HANDOFF:line; the orchestrator captures it and threads an accumulating context block into later step prompts, so e.g. a PR number from/pr openreaches a later/pr addresswithout re-typing.saveforwards input — composite skills generated from a parameterized flow pass their text through to/flow go.flow-template.md,step-template.md),help.md, anddocs/skills/flow.mdupdated.Example:
Validation
mise run skills:validate—flowPASSES (2 remaining failures indev-docs/docsare pre-existing, identical onmain)mise run docs:build— clean;docs/skills/flow.mdrendersnew/go/status/save/list) resolve--globalvia the sharedflow-dir.mdFuture Work
{{steps.pr_open.number}}) as a deterministic alternative to LLM-mediated flow context, if precision is ever needed.flow rm/flow editfor lifecycle management of saved (esp. global) flows.