| name | code-review |
| description | Review Gradient docs, profiles, schemas, and harness changes for public-safe
boundaries, lifecycle consistency, and contract depth. Trigger:
/code-review, /review, /critique.
|
| argument-hint | [branch|diff|files] |
/code-review
Review in this repo is contract review first. There is little code today, so
the main failure modes are leaked private context, shallow module boundaries,
profile forks, and docs that contradict the lifecycle.
Required Checks
- Public-safe boundary:
- no customer names, private repo names, credentials, transcripts, private
prompts, raw client telemetry, or deployment-specific config;
- synthetic fixtures are clearly synthetic.
- Lifecycle consistency:
- every feature names the strengthened stage in
Intent -> Work Graph -> Fleet Run -> Evidence -> Policy/Eval -> Feedback;
- docs do not rename or reorder the invariant without a decision-log entry.
- Module boundaries:
- Harness, Work, Fleet, Policy, and Context stay deep;
- provider/task/runtime/retrieval quirks stay behind adapters.
- Profile semantics:
- profiles configure deployment differences;
- they do not fork module semantics per customer.
- Evidence:
- schema/profile changes name validation evidence or clearly mark the path
unverified.
Gate
The load-bearing ship gate is ./scripts/validate.sh, plus reviewer
judgment for lifecycle semantics in docs/architecture.md and
docs/module-contracts.md when docs change.
Output
Lead with blocking findings ordered by severity. Include file references and the
smallest correction that would make the change shippable.
