feat(ce-commit-push-pr): skip evidence prompt when judgment allows#663
feat(ce-commit-push-pr): skip evidence prompt when judgment allows#663
Conversation
Two new short-circuits run before the categorical skip ladder: if the user explicitly requested evidence, proceed to capture with graceful fallback; if the agent authored the commits this session and knows the change is non-observable, skip the prompt without asking. The blocking prompt was the most expensive step in the workflow and rarely adds value when the agent already knows the change it just wrote.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d4e7a59fc7
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| 1. **User explicitly asked for evidence.** If the user's invocation requested it ("ship with a demo", "include a screenshot"), proceed directly to capture. If capture turns out to be not possible (no runnable surface, missing credentials, docs-only diff) or clearly not useful, note that briefly and proceed without evidence — do not force capture for its own sake. | ||
|
|
There was a problem hiding this comment.
This short-circuit now sends every explicit evidence request directly to ce-demo-reel, which can bypass the existing Use existing evidence path when the user already supplied a valid URL/embed (e.g., “include this screenshot”). In that case, if capture is infeasible (docs-only diff, missing credentials, non-runnable surface), the new flow can proceed without evidence even though reusable evidence was already available, which is a behavior regression from the prior decision ladder.
Useful? React with 👍 / 👎.
PR #663 squash-merged as `feat(ce-commit-push-pr):` — adding two short-circuits that skip a blocking prompt when the agent just authored the change. The intent was a UX/flow fix, not a new capability, so the correct conventional prefix is `fix:`. Since the prefix drove a minor bump, the open release PR (#661) is pinning the linked `cli` / `compound-engineering` group at 3.1.0. This empty commit reclassifies the pending release to 3.0.2 via `Release-As:` footers so the patch-level fixes in this window (#660 ce-update, #664 ce-demo-reel, #663 ce-commit-push-pr) land as 3.0.2 instead of 3.1.0. The feat prefix remains in history and may still render under a Features heading in the generated changelog — hand-edit the release PR body before merge if so. Release-As: cli@3.0.2 Release-As: compound-engineering@3.0.2
1 participant
Summary
ce-commit-push-prpreviously walked the full evidence-decision ladder on every invocation, asking a blocking user question whenever the branch diff showed observable behavior. That prompt fires often on chainedce-commit→ce-commit-push-prruns, where the agent just authored the commits and already knows the change's character — so the prompt rarely adds value and interrupts flow.Two short-circuits now run before the full decision:
The full decision still runs for cold invocations and ambiguous changes; standalone use is unaffected.