Skip to content

Commit 59135ca

Browse files
committed
fix(coderabbit): limit neighbouring review scope creep
1 parent 91121ff commit 59135ca

1 file changed

Lines changed: 13 additions & 11 deletions

File tree

‎.coderabbit.yaml‎

Lines changed: 13 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -48,17 +48,19 @@ reviews:
4848
instructions: >-
4949
Act as an adversarial second-opinion reviewer. Verify PR claims against implementation and
5050
contracts. Trace changed inputs through normal, boundary, error, cancellation, retry, and
51-
default paths and their consumers. Seek plausible counterexamples and regressions from removed
52-
safeguards. Identify assumptions in changed code that depend on facts outside the diff. First
53-
verify repository conventions, tests, and related implementations. When a potential finding
54-
depends on external behavior, use web search and prefer official documentation, specifications,
55-
or upstream repositories. Report only concrete, actionable conflicts or failure modes, citing
56-
the relevant repository location or external source. Prioritize correctness, security, data loss,
57-
lifecycle, and test gaps. Do not report generic best practices, unsupported concerns, speculative
58-
style comments, or unrelated refactors. When changed code introduces a local implementation of a
59-
cross-cutting concern, check whether it bypasses or duplicates an established repository abstraction
60-
or nearby convention. Report only a concrete inconsistency with behavioral or maintenance impact,
61-
and allow intentional deviations.
51+
default paths and their direct test counterparts. Do not flag defects in files not changed by
52+
this PR unless the defect is directly triggered by changed code and cannot be detected in the
53+
changed file alone. Seek plausible counterexamples and regressions from removed safeguards.
54+
Identify assumptions in changed code that depend on facts outside the diff. First verify
55+
repository conventions, tests, and related implementations. When a potential finding depends on
56+
external behavior, use web search and prefer official documentation, specifications, or upstream
57+
repositories. Report only concrete, actionable conflicts or failure modes, citing the relevant
58+
repository location or external source. Prioritize correctness, security, data loss, lifecycle,
59+
and test gaps. Do not report generic best practices, unsupported concerns, speculative style
60+
comments, or unrelated refactors. When changed code introduces a local implementation of a
61+
cross-cutting concern, check whether it bypasses or duplicates an established repository
62+
abstraction or nearby convention. Report only a concrete inconsistency with behavioral or
63+
maintenance impact, and allow intentional deviations.
6264
6365
- path: "**/*.{ts,tsx,js,jsx,mts,mjs,cts,cjs}"
6466
instructions: >-

0 commit comments

Comments
 (0)