Repository navigation
Expand file tree
/
Copy path.coderabbit.yaml
More file actions
109 lines (96 loc) · 4.48 KB
/
Copy path.coderabbit.yaml
File metadata and controls
109 lines (96 loc) · 4.48 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
language: en-US
tone_instructions: >-
Be concise and evidence-driven. Prioritize correctness, lifecycle, compatibility,
and missing verification over style-only feedback.
reviews:
profile: assertive
request_changes_workflow: false
high_level_summary: true
high_level_summary_instructions: |
Summarize user-visible behavior, compatibility or provenance implications,
verification actually present in the pull request, and any unverified scope.
Keep performance, numerical correctness, capacity, lifecycle, and quality
claims separate.
merge_risk_instructions: |
Treat changes to workload semantics, planning, scheduling, ownership/fencing,
recovery, checkpoints, distributed topology, tensor contracts, CUDA kernels,
training objectives, public configuration, and release provenance as high risk.
Documentation-only and test-only changes are lower risk only when they do not
alter shipped recipes, public claims, or executable contracts.
sequence_diagrams: false
poem: false
auto_review:
enabled: true
auto_incremental_review: true
drafts: false
auto_approvals:
enabled: false
path_instructions:
- path: "aspec/{planning.py,topology.py,evidence.py,reporting.py,runtime_identity.py,work_lifecycle.py}"
instructions: |
Verify that workload semantics, available capability, selected Plan, and
observed Evidence remain distinct. Required capabilities must fail closed;
fallback, omission, requested/effective values, and unknown observations
must remain explicit. Check memory and capacity accounting by resource class.
- path: "aspec/{controller,ray,transfer,offline}/**"
instructions: |
Review stable work identity, exactly-once committed work, bounded admission,
lease ownership, fencing, terminal states, and cleanup on success, failure,
cancellation, and recovery. Flag races, early reclamation, cross-run cleanup,
silent remote fallback, and incomplete finite-tail handling.
- path: "aspec/{training,data}/**"
instructions: |
Check packing and regrouping preserve document boundaries, supervision,
positions, source identity, optimizer-step semantics, resume state, and RNG.
Changes to algorithms, objectives, checkpoint formats, or export assets need
focused compatibility tests and must not conflate functional, numerical,
lifecycle, throughput, or quality evidence.
- path: "aspec/{models,kernels,inference}/**"
instructions: |
Prioritize tensor shape/layout/dtype/device contracts, distributed geometry,
masking and normalization semantics, numerical stability, autograd behavior,
synchronization, aliasing, stream lifetime, and bounded specialization.
Require evidence appropriate to CPU, GPU, CUDA Graph, multi-GPU, or
multi-node behavior; a skipped GPU test is not acceptance evidence.
- path: "aspec/compat/**"
instructions: |
Confirm compatibility code stays narrow and version-pinned. For copied or
adapted upstream content, verify source/revision attribution, modification
notes, inherited notices, license texts, and contract tests remain complete.
- path: "tests/**"
instructions: |
Check that tests exercise observable behavior and failure paths without
weakening assertions to manufacture agreement. GPU and integration gates
must remain explicit; mocks or skips must not be presented as hardware,
numerical, performance, lifecycle, or quality acceptance.
- path: "{configs,docs,examples,.github}/**"
instructions: |
Keep public behavior, recipes, support boundaries, examples, CI, and claims
aligned with implementation. Performance claims need comparable workload,
hardware/software identity, statistics, correctness evidence, and explicit
limitations. Do not expose credentials, private data, weights, or local paths.
tools:
ruff:
enabled: true
config_file: pyproject.toml
pylint:
enabled: false
flake8:
enabled: false
markdownlint:
enabled: false
shellcheck:
enabled: true
actionlint:
enabled: true
github-checks:
enabled: true
knowledge_base:
code_guidelines:
enabled: true
filePatterns:
- AGENTS.md
- CONTRIBUTING.md
- docs/framework/ARCHITECTURE.md
- docs/framework/DECISIONS.md