Review Ontime changes
Review as a maintainer. Find material defects, not speculative advice, style preferences, or generic checklists. Approve when no material issue remains.
Load relevant context
Read the full diff, PR description, linked issue, tests, and nearby owning code. Then load only applicable guides:
- Every non-trivial review: change assessment
- Module placement, server layers, client state, shared packages: architecture
- Tests or changed behaviour: testing
- Comments, abstractions, naming, complexity: code quality
- Authentication, external input, files, integrations, assets, secrets: security
- Routes, URLs, websockets, authentication, cookies, presets, assets: routing and cloud
- Rundowns, timers, persistence, imports, cache, realtime: domain invariants
- Commands, imports, dependencies, formatting, CI claims: workflow
Check a guide and nearby canonical code before citing an Ontime convention. Skip unrelated guides.
Review order
- Establish intent and affected runtime surfaces.
- Read tests first. Identify claimed behaviour and coverage.
- Trace implementation, errors, and state transitions.
- Check correctness/data integrity, security, architecture/testability, cloud routing, lifecycle/performance, maintainability.
- Verify claimed checks. Never claim unobserved results.
Passing tests do not prove architecture, routing, comments, or error paths. Review changed behaviour only; include existing problems only when the diff worsens or relies on them.
Findings
Report only concrete, actionable issues. Each finding: tight line range, direct defect, impact and trigger, smallest viable remedy when unclear.
- P0 — Critical: data loss, exploitable vulnerability, broadly broken production. Blocks merge.
- P1 — High: likely correctness failure or major supported-deployment regression. Blocks merge.
- P2 — Medium: real edge-case defect, architecture regression, missing business-rule test, stale comment, meaningful maintenance risk. Normally blocks merge.
- P3 — Low: local improvement with limited impact. No subjective style or tool-managed formatting.
Order by priority. Prefer few high-confidence findings. No praise or checklist before findings. If none, say so and note verification gaps or residual risk.
Then give one concise PR-level value/risk/complexity assessment. Never repeat it per finding.
1---2name: code-review3description: Review Ontime changes for concrete correctness, architecture, testing, routing, security, and maintenance issues. For GitHub Copilot review.4---56# Review Ontime changes78Review as a maintainer. Find material defects, not speculative advice, style preferences, or generic checklists. Approve when no material issue remains.910## Load relevant context1112Read the full diff, PR description, linked issue, tests, and nearby owning code. Then load only applicable guides:1314- Every non-trivial review: [change assessment](../../../docs/agent-guides/change-assessment.md)15- Module placement, server layers, client state, shared packages: [architecture](../../../docs/agent-guides/architecture.md)16- Tests or changed behaviour: [testing](../../../docs/agent-guides/testing.md)17- Comments, abstractions, naming, complexity: [code quality](../../../docs/agent-guides/code-quality.md)18- Authentication, external input, files, integrations, assets, secrets: [security](../../../docs/agent-guides/security.md)19- Routes, URLs, websockets, authentication, cookies, presets, assets: [routing and cloud](../../../docs/agent-guides/routing-and-cloud.md)20- Rundowns, timers, persistence, imports, cache, realtime: [domain invariants](../../../docs/agent-guides/domain-invariants.md)21- Commands, imports, dependencies, formatting, CI claims: [workflow](../../../docs/agent-guides/workflow.md)2223Check a guide and nearby canonical code before citing an Ontime convention. Skip unrelated guides.2425## Review order26271. Establish intent and affected runtime surfaces.282. Read tests first. Identify claimed behaviour and coverage.293. Trace implementation, errors, and state transitions.304. Check correctness/data integrity, security, architecture/testability, cloud routing, lifecycle/performance, maintainability.315. Verify claimed checks. Never claim unobserved results.3233Passing tests do not prove architecture, routing, comments, or error paths. Review changed behaviour only; include existing problems only when the diff worsens or relies on them.3435## Findings3637Report only concrete, actionable issues. Each finding: tight line range, direct defect, impact and trigger, smallest viable remedy when unclear.3839- **P0 — Critical:** data loss, exploitable vulnerability, broadly broken production. Blocks merge.40- **P1 — High:** likely correctness failure or major supported-deployment regression. Blocks merge.41- **P2 — Medium:** real edge-case defect, architecture regression, missing business-rule test, stale comment, meaningful maintenance risk. Normally blocks merge.42- **P3 — Low:** local improvement with limited impact. No subjective style or tool-managed formatting.4344Order by priority. Prefer few high-confidence findings. No praise or checklist before findings. If none, say so and note verification gaps or residual risk.4546Then give one concise PR-level value/risk/complexity assessment. Never repeat it per finding.
cpvalente