feat(workflows): add --dry-run flag to specify workflow run#2704
feat(workflows): add --dry-run flag to specify workflow run#2704fuleinist wants to merge 8 commits into
Conversation
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Adds a workflow “dry-run” mode to preview rendered inputs and skip AI/interactive execution, and exposes it via CLI entrypoints.
Changes:
- Introduces
dry_runonWorkflowEngine.execute()and propagates it throughStepContext. - Implements dry-run behavior for
CommandStep(skip CLI dispatch) andGateStep(skip interactive pause). - Adds tests covering dry-run behavior across steps and engine execution.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| tests/test_workflows.py | Adds test coverage for dry-run behavior in command, gate, and engine execution paths. |
| src/specify_cli/workflows/steps/gate/init.py | Skips interactive gating and returns COMPLETED during dry-run. |
| src/specify_cli/workflows/steps/command/init.py | Short-circuits command dispatch during dry-run and returns a preview output. |
| src/specify_cli/workflows/engine.py | Adds dry_run parameter to execute() and passes it to StepContext. |
| src/specify_cli/workflows/base.py | Extends StepContext with a dry_run flag. |
| src/specify_cli/init.py | Adds dry-run CLI options and new direct “specify/plan” CLI commands. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Please address Copilot feedback |
7a3db5a to
d271c5c
Compare
|
All four review items addressed in the latest commits:
Branch rebased onto latest main and force-pushed to |
There was a problem hiding this comment.
Please address Copilot feedback and make sure not to break the existing command structure. The "--dry-run" should not introduce new commands. Note that the specify CLI is NOT the command executor. Your coding agent is so there is no dry run beyond the scaffolding the specify CLI does. Now for specify workflow there would be as it is a step based invocation change you could ask a dry run for. Please readjust this according to this design. Thanks!
|
Review 4382194003 addressed. Summary:
Follow-up items for next PR:
Commit: 6a074ba on feat/2661-dry-run |
- Add start_at/stop_after params to WorkflowEngine.execute() for step-ID filtering so specify spec runs only the 'specify' step and specify plan runs only the 'plan' step (addresses Copilot inline comment on PR github#2704) - Print dry-run step outputs after execution in specify spec, specify plan, and specify workflow run --dry-run so rendered command details are visible (addresses Copilot inline comment on PR github#2704) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Fixed in latest commit (8fa7bbc): Item #10 (step isolation): Added Item #11 (dry-run output): After execution, Commit: 8fa7bbc on |
c2868d7 to
721ef9a
Compare
JSON output stream stays clean:
- workflow_run now suppresses the dry-run banner (and any future
per-step chatter would also be silenced — they already run
after the early return for --json) when --json is set, so a
single well-formed JSON object lands on stdout.
- The existing _stdout_to_stderr_when(json_output) context already
protects engine.execute(); the banner was the one stray print
outside that context.
Gate dry-run output contract:
- Preserve the original output['message'] (the gate prompt) so
downstream steps referencing {{ steps.<id>.output.message }}
during a dry-run still see the prompt text. The DRY RUN preview
now lives on output['dry_run_message']. The CLI rendering loop
reads dry_run_message first, falls back to message for custom
step types.
- Normalize options defensively: a workflow that bypasses
validation may set options to a non-list (string, dict, scalar).
options[0] in the dry-run branch would index into a string or
raise on a dict. Now coerced to []; choice is None.
Tests:
- test_dry_run_skips_interactive_gate: assert message is the
original prompt and dry_run_message contains the DRY RUN preview.
- New test_dry_run_normalizes_non_list_options covering None,
string, dict, int, and empty string for the options field.
|
Hi @mnriem - I've addressed the Copilot review comments and removed --dry-run from the specify spec/plan commands per your feedback. The --dry-run flag is now only available on specify workflow run, which is the step-based invocation path. The CLI scaffolding commands (specify spec, specify plan) do not accept --dry-run. Summary of changes:
The code now has an explicit NOTE explaining that specify spec/plan were intentionally not added to the CLI. Please let me know if you'd like me to address anything else! |
- CommandStep dry-run now sets output['executed'] = False so
downstream branching/conditions can distinguish a preview from
a real successful run. exit_code is kept at 0 for backward
compatibility (and because the step status is COMPLETED).
- GateStep dry-run choice no longer blindly picks options[0]:
it skips reject/abort sentinels and falls through to the first
non-sentinel option, or None if every option is a sentinel.
This avoids dry-run unintentionally steering downstream
branching when the first option happens to be a reject.
- GateStep options normalization now accepts any
collections.abc.Sequence other than str/bytes (so tuples work,
not just lists). Dict, scalar, str, and bytes are still rejected
as before.
- New tests:
- test_dry_run_accepts_tuple_options
- test_dry_run_skips_reject_sentinels_for_choice (covers
first-sentinel skip and all-sentinel fallthrough to None)
- test_dry_run_returns_completed_without_dispatch now also
asserts output['executed'] is False
|
Hi @mnriem — all Copilot feedback has been addressed in the latest commits:
Latest commit: 7f717e0 Please let me know if there's anything else to address. Happy to iterate further! |
- gate/__init__.py: move 'import collections.abc' to module scope (per-call overhead + shorter execute()). - gate/__init__.py: empty options in the non-dry-run interactive path would IndexError in _prompt (it formats 'Choose [1-N]' and defaults to options[-1] on EOF). Normalization runs regardless of dry_run, so a workflow that bypassed validation and produced options=[] would crash. Now the interactive path returns StepStatus.FAILED with a clear error before calling _prompt(). The dry-run path is unchanged: it still produces options=[] / choice=None safely. - command/__init__.py: also populate output['dry_run_message'] in CommandStep's dry-run branch. The CLI render loop prefers dry_run_message and falls back to message, so without this the two step types had different output contracts. Both fields now hold the same preview string, keeping the loop simple. - New test test_interactive_path_fails_on_empty_options covers the FAILED path. Existing test_dry_run_returns_completed_without_dispatch now also asserts dry_run_message == message.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Copilot's findings
Comments suppressed due to low confidence (1)
src/specify_cli/workflows/steps/command/init.py:129
- When a command dispatch occurs,
output['executed']should be set toTrueso downstream expressions can distinguish a real invocation from a dry-run preview (whereexecutedis forced toFalse).
if dispatch_result is not None:
output["exit_code"] = dispatch_result["exit_code"]
output["stdout"] = dispatch_result["stdout"]
output["stderr"] = dispatch_result["stderr"]
output["dispatched"] = True
- Files reviewed: 6/6 changed files
- Comments generated: 3
- PromptStep now honors context.dry_run: renders a preview with
executed=False, dispatched=False, exit_code=0, dry_run=True,
and a DRY RUN message. Without this, a workflow with
type: prompt would still spawn the integration CLI even in
dry-run mode, contradicting the docstring claim that dry_run
skips AI invocation across the board.
- workflow_run's dry-run preview loop is no longer gated on
state.status == 'completed'. Dry-run previews print regardless
of the run's final status (completed / failed / paused), so a
dry-run that fails mid-run still surfaces the prompts / command
invocations that would have been resolved up to the point of
failure. The --json branch is still suppressed (the early
return for json_output returns before the loop).
- CommandStep real-run path now sets output['executed'] = True,
and the no-dispatch (CLI-not-found) branch sets it False. The
dry-run branch already sets it False. Downstream
{{ steps.<id>.output.executed }} expressions can now reliably
key on the field regardless of which branch executed.
- New test test_dry_run_prompt_short_circuits covers PromptStep
dry-run. Existing test_dispatch_with_mock_cli now also asserts
executed is True on the real-run success path.
mnriem
left a comment
There was a problem hiding this comment.
Please address Copilot feedback
|
Hi @mnriem — all Copilot feedback from the 2026-06-01 cycle has been addressed in commit 608d414 (pushed 2026-06-08):
Would you mind taking another look? #2704 |
Summary
Implements issue #2661 — add a
--dry-runflag tospecify workflow runthat previews each step's resolved inputs, prompt, and command invocation without spawning the underlying coding-agent CLI or making any AI calls. Use it to verify what a workflow would dispatch before running for real.What ships
Engine
src/specify_cli/workflows/base.py:StepContextgainsdry_run: bool = Falsesrc/specify_cli/workflows/engine.py:WorkflowEngine.execute(..., dry_run=False)propagates the flag to every stepdry_runonRunState(save/load) and restores it inresume()so an interrupted dry-run does not silently become a real rundry_runsemantics documented in theexecute()docstringStep behavior
CommandStep(workflows/steps/command/):dry_run=Truerenders the integration'sbuild_command_invocation(command, args)preview, setsexit_code=0, returnsCOMPLETEDwithout spawning the CLIGateStep(workflows/steps/gate/):dry_run=TruereturnsCOMPLETEDimmediately with a short DRY RUN message; no interactive promptbuild_command_invocation: preview includes the command name and a one-line note explaining the fallbackexceptclause narrowed from bareExceptionto(ImportError, AttributeError, KeyError, TypeError, ValueError)so dry-run failures stay debuggableCLI
specify workflow run --dry-run(in-module, in__init__.py) — the only place the flag is exposed. After the run, the CLI prints anyoutput['dry_run']messages so the rendered previews surface in the terminal.What does not ship (intentional)
Per design review, the
specifyCLI is scaffolding + workflow orchestration only. The per-stage surface (/speckit.specify,/speckit.plan, ...) belongs to the agent, not the CLI. A previous draft of this PR addedspecify spec/specify planpreview commands; those have been removed along with the supportingstart_at/stop_afterstep filtering in the engine. Issue #2661's wording has been re-scoped to--dry-runonspecify workflow run.Tests
tests/test_workflows.pytest_dry_run_persisted_in_run_state:dry_runsurvives save/load round-triptest_resume_restores_dry_run:resume()rebuildsStepContextwith the persisted flag so an interrupted dry-run stays a dry-runtest_dry_run_returns_completed_without_dispatch:CommandStepreturnsCOMPLETEDwith the rendered preview; no CLI is spawned; usestmp_pathfor portabilitytest_dry_run_skips_interactive_gate:GateStepshort-circuits with a DRY RUN messageUsage
Closes #2661