chore: add Codex setup guidelines#1437
Conversation
Add project-local Codex hook configuration and document commit message expectations for agent-created changes. Commit subjects should follow Conventional Commits, and non-trivial changes should include a body describing the motivation, implementation notes, and validation.
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Pull request overview
This PR adds repository-local Codex configuration guidance so local AI tooling follows the same Rust formatting/linting workflow already used elsewhere, while also documenting commit message expectations for contributors.
Changes:
- Add
.codex/hooks.jsonwith a post-tool hook that runs Rust formatting and lint checks after Rust file edits. - Add
.codex/.gitignoreso local-only Codexconfig.tomldoes not get committed. - Document Conventional Commits and recommended commit body content in
AGENTS.md.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
AGENTS.md |
Adds commit message guidance for contributors and agents. |
.codex/hooks.json |
Introduces shared Codex hook configuration mirroring existing Rust check automation. |
.codex/.gitignore |
Keeps local Codex config out of version control. |
Summary
.codex/.config.tomlfrom the repository.AGENTS.md.Details
Commit subjects should follow Conventional Commits. For non-trivial changes, commits should also include a body describing why the change was made, notable implementation details, and validation performed.
Validation
jq empty .codex/hooks.jsongit diff --checkSummary by CodeRabbit
Chores
Documentation