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 11 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 |
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 |
|
Please address Copilot feedback |
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
|
Please address Copilot feedback |
Re: review #4382194003 (CHANGES_REQUESTED) — design re-scopedThanks for the design guidance. The PR has been reworked to match —
Tests: I've already used my remaining reviewer-request slot trying to re-request review (API returns 404 from my fork-side, presumably a permissions boundary on the upstream repo). If you have a moment, could you re-review when convenient? Happy to address anything else you spot. |
| else: | ||
| invoke_str = impl.build_command_invocation(command, args_str) |
|
Please address Copilot feedback |
1. command/__init__.py: Fix syntax error - else: block body was at 0 indentation instead of 24 spaces (inside the 'if impl is None' else branch). Also try/except structure was broken with except at same level as try but body leaking outside. 2. __init__.py: Guard the dry-run preview loop with 'and not json_output' so that --json mode emits only a single well-formed JSON object without per-step dry-run text polluting stdout. Fixes Copilot comments: - 3383108299 (SyntaxError from mis-indented invoke_str) - 3379546978 (mis-indentation issue) - 3379547033 (dry-run loop running with --json enabled)
|
All Copilot inline comments have been addressed in the latest commits:
All previous inline comment threads are already replied to with specific fix details. Ready for your re-review when available. |
fuleinist
left a comment
There was a problem hiding this comment.
Hi @mnriem — all Copilot feedback from the June9 cycle has been addressed in the latest commit (b82db41). Summary of fixes:\n\n1. command/init.py: Fixed syntax error — the else: block body was at0 indentation instead of inside the 'if impl is None' else branch. Also fixed the try/except structure.\n\n2. init.py: Guarded the dry-run preview loop with 'and not json_output' so --json mode emits only a single well-formed JSON object.\n\nThe PR head is b82db41. Ready for your re-review when you have a moment.
| def test_execute_dry_run(self, project_dir): | ||
| """Dry-run: engine returns COMPLETED without invoking the AI for command steps.""" | ||
| from unittest.mock import patch | ||
| from specify_cli.workflows.engine import WorkflowEngine, WorkflowDefinition | ||
| from specify_cli.workflows.base import RunStatus |
There was a problem hiding this comment.
Thanks — addressed in abedc58: abedc58
Added two CLI-level tests using Typer's CliRunner (matching the existing pattern in TestWorkflowJsonOutput):
test_run_dry_run_flag_wires_through_cli— invokesspecify workflow run <wf> --dry-runagainst a gated workflow, asserts the DRY-RUN banner is printed, the per-step[DRY RUN]preview body is emitted, the gate short-circuits toStatus: completed(noResume with:hint).test_run_dry_run_with_json_suppresses_banner_and_previews— same workflow under--dry-run --json, asserts stdout is a single JSON object withstatus: completedand no banner/preview leakage.
All 217 tests in tests/test_workflows.py pass.
| dry_run: bool = typer.Option( | ||
| False, "--dry-run", help="Show the rendered prompt/inputs for each step without invoking the AI" | ||
| ), |
There was a problem hiding this comment.
Thanks — addressed in abedc58: abedc58
Help text now states the --json suppression explicitly:
dry_run: bool = typer.Option(
False,
"--dry-run",
help=(
"Show the rendered prompt/inputs for each step without invoking the AI. "
"Suppressed when --json is set so the JSON object is the only thing on stdout."
),
),Also added a CLI-level test (test_run_dry_run_with_json_suppresses_banner_and_previews) that asserts the banner and per-step preview lines are absent from stdout under --dry-run --json.
|
Please address Copilot feedback |
…ests Address Copilot review comments 3391287191 and 3391287148 from 2026-06-10. 3391287191 (src/specify_cli/__init__.py): The --dry-run help text said it would 'Show the rendered prompt/inputs' but the implementation intentionally suppresses the banner and per-step previews when --json is set. Update the help text to call this out so automation/CI users aren't surprised. 3391287148 (tests/test_workflows.py): The --dry-run behavior was only validated via WorkflowEngine.execute(..., dry_run=True). Add CLI-level tests using Typer's CliRunner to cover the user-facing entrypoint: * test_run_dry_run_flag_wires_through_cli -- verifies the DRY-RUN banner, per-step previews, and that the gate is short-circuited end-to-end (Status: completed, no 'Resume with:' hint). * test_run_dry_run_with_json_suppresses_banner_and_previews -- verifies that --dry-run together with --json does NOT print the banner or per-step previews; stdout is a single JSON object with status 'completed'. Both tests use the existing _write_wf / _invoke pattern from TestWorkflowJsonOutput. All 217 tests in tests/test_workflows.py pass.
|
Hi @mnriem — noted that the review cycle has repeated several times now (each Copilot re-review seems to surface additional comments). To help break the loop: can you confirm whether the current head commit (post June 10 syntax-fix push) is in a reviewable state from your perspective, or is there a specific outstanding item you'd like addressed before you can give a final review? Happy to scope the PR down further if that would help. |
|
Hi @mnriem — following up on your review from May 28. The PR has been updated to remove the per-stage \specify spec\ and \specify plan\ commands entirely. --dry-run\ now only exists on \specify workflow run, which aligns with your design point that the CLI is scaffolding/workflow-orchestration only, not a command executor. The PR description now explicitly states: 'Per design review, the \specify\ CLI is scaffolding + workflow orchestration only. The per-stage surface belongs to the agent, not the CLI.' Is the updated scope acceptable for approval, or are there remaining concerns? |
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