Back to Signal Feed
CodeTracked since May 21, 2026

Add inline base-branch and instruction support to /local-review

The `/local-review` command now accepts optional trailing text: a single token is parsed as the base branch to compare against, while multi-word input is treated as review instructions (usable via `base -- instructions`), with Kilo-specific parsing moved into review-session helpers.

local-reviewreview/session helpersopencodebase branch

What Happened

  • The `/local-review` command now accepts optional trailing text: a single token is parsed as the base branch to compare against, while multi-word input is treated as review instructions (usable via `base -- instructions`), with Kilo-specific parsing moved into review-session helpers.
  • The `/local-review` command now accepts optional trailing text: a single token is parsed as the base branch to compare against, while multi-word input is treated as review instructions (usable via `base -- instructions`), with Kilo-specific parsing moved into review-session helpers.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Introduced command parsing for optional `/local-review` arguments so developers can set a compare branch and pass extra review instructions in one call; the logic is implemented in Kilo’s review/session helpers with a narrow hook change in shared opencode code.

Why Track This

Why It Matters

Developers using `/local-review` can now target a specific base branch and supply custom review guidance without an extra blocking step, which makes review sessions faster and keeps the workflow less interrupted by follow-up prompts. The parser now maps a single token to base-branch selection and multi-word text to instruction content via `base -- instructions`, while shared runtime paths stay mostly untouched; continue monitoring for parsing edge cases (e.g., odd branch-name patterns) that could direct reviews to the wrong base or drop instruction text.

Impact

Developers using `/local-review` can now target a specific base branch and supply custom review guidance without an extra blocking step, which makes review sessions faster and keeps the workflow less interrupted by follow-up prompts. The parser now maps a single token to base-branch selection and multi-word text to instruction content via `base -- instructions`, while shared runtime paths stay mostly untouched; continue monitoring for parsing edge cases (e.g., odd branch-name patterns) that could direct reviews to the wrong base or drop instruction text.

What To Watch Next

  • Watch whether local-review becomes a repeated pattern.
  • Track follow-up changes around AI Code Review.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: base_branch_name_ambiguity, instruction_delimiter_collision.
Open Topic TimelineOpen Technical EventOpen Original Sourcebase_branch_name_ambiguity / instruction_delimiter_collision / shared_hook_regression_risk

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

Kilo-Org/kilocode PR #9951: feat(cli): accept local-review input

A single argument is treated as the base branch to compare against, while multi-word input is appended to the review prompt as additional instructions.