palarran-code-review

Topics in the source

• Review an existing change

Start with task context and the review workflow. Read only relevant target instructions and source guidance; ordinary small reviews do not require the full planning/build contracts. Apply Code review domain rules. /palarran:code:review {range?} binds exact base/head commits and diff semantics; with no range, use the clearly identified current change or ask when ambiguous. Preserve dirty work and label it separately. --plan returns scope/check suggestions from visible context only: no file reads, writes, Git/tool execution or network. Inspect changed code and the necessary callers, state owners and tests. Follow input → state → side effect → acknowledgement, including errors, retries, duplicates, concurrency and shutdown where relevant. Findings need concrete location, trigger, impact, counterevidence and safe retest; distinguish source-supported defects, executed reproductions and suspected hypotheses. Avoid style noise and unrelated cleanup. No findings is not proof of correctness. Use existing project tests only under already authorized commands/fixture scope. A fake-provider PASS does not prove live integration; mark missing checks NOTRUN. The project-tests adapter is optional a

This is an excerpt. Refer to the complete source and its current requirements.