Skip to content

Fix review interactive setup and Codex defaults - #1749

Merged
dipree merged 6 commits into
mainfrom
fix/review-interactive-codex-regressions
Jul 14, 2026
Merged

Fix review interactive setup and Codex defaults#1749
dipree merged 6 commits into
mainfrom
fix/review-interactive-codex-regressions

Conversation

@entire

@entire entire Bot commented Jul 14, 2026

Copy link
Copy Markdown

https://entire.io/gh/entireio/cli/trails/854

This draft pull request was opened by Entire after CI was requested for the linked trail. Feel free to edit the title or body — the link above is what keeps the trail and PR connected.

dipree added 2 commits July 14, 2026 18:37
Entire-Checkpoint: 01KXGQW0RDC3PF5QKT23GN0B83
Entire-Checkpoint: 01KXGS1Y108CS4JZGG4988H6Q9
@dipree
dipree marked this pull request as ready for review July 14, 2026 16:58
@dipree
dipree requested a review from a team as a code owner July 14, 2026 16:58
Copilot AI review requested due to automatic review settings July 14, 2026 16:58

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adjusts the entire review command’s interactive-setup gating and updates Codex default/legacy review configuration so Codex runs prompt-only rather than relying on a removed curated /review skill.

Changes:

  • Adds a compatibility repair that rewrites legacy Codex reviewer configs using Skills: ["/review"] into prompt-only configs at runtime.
  • Centralizes review interactivity detection (reviewCommandIsInteractive) and uses it across --edit, guided setup, multi/single-agent sink selection, and findings picking.
  • Updates defaults/tests so Codex (and other non-Claude agents) use a prompt-based default instead of a curated skill.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
cmd/entire/cli/review/profile.go Repairs legacy Codex /review skill configs in-memory and makes Codex defaults prompt-only.
cmd/entire/cli/review/fix.go Uses unified review interactivity detection for findings selection.
cmd/entire/cli/review/configure_test.go Adds coverage for Codex prompt-only defaults, legacy repair, and interactivity logic.
cmd/entire/cli/review/cmd.go Introduces reviewCommandIsInteractive/reviewTTYIsInteractive and wires them into review flows.
cmd/entire/cli/review/cmd_test.go Adds regression test ensuring legacy Codex configs still launch; updates invalid-skill coverage.
cmd/entire/cli/interactive/interactive.go Adds IsTerminalReader helper for stdin TTY detection.

Comment thread cmd/entire/cli/review/cmd.go Outdated
dipree added 4 commits July 14, 2026 19:04
Entire-Checkpoint: 01KXGSC7YR34K5TTMAVFH7PCMA
Entire-Checkpoint: 01KXGSRY52644B5B6A7CKHQV4B
Entire-Checkpoint: 01KXGT7DJ8E7EC047SBCZXN1Z3
Entire-Checkpoint: 01KXGTKA4VF60BYNEPDWQQ3NNC
@peyton-alt
peyton-alt enabled auto-merge July 14, 2026 18:14
@dipree
dipree disabled auto-merge July 14, 2026 20:01
@dipree
dipree merged commit cd6155e into main Jul 14, 2026
10 checks passed
@dipree
dipree deleted the fix/review-interactive-codex-regressions branch July 14, 2026 20:01
peyton-alt added a commit that referenced this pull request Jul 14, 2026
… native invocation

The user asked whether configured codex $code-reviewer skills are
retained after #1749's legacy-config repair merged in. They are, by two
independent guards; these tests lock that so a future migration edit
can't clobber real skills:

- normalizeLegacyCodexDefaultSkills only rewrites codex's exact
  ["/review"] artifact; a $code-reviewer config and multi-skill
  configs pass through untouched.
- codexNativeSkillInvocations rewrites only slash-form to $; $name and
  plain text pass through verbatim.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Entire-Checkpoint: 01KXHANJCZ4G2GCS548V1CKZSS
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants