// Project code conventions reference. Covers typing, structure, DI, testing, and anti-pattern rules for module implementation.
Adversarial PR code review using Codex CLI. Codex review (~20-50 min) -> structured findings -> HITL approval -> fix loop.
OpenSpec context documentation policy: keep requirements in spec.md and capture narrative context in context/overview/rationale docs under openspec/specs. Use when creating or updating OpenSpec docs, spec context, or onboarding/guide documentation.
| name | project-conventions |
| description | Project code conventions reference. Covers typing, structure, DI, testing, and anti-pattern rules for module implementation. |
| metadata | {"author":"codex-lb","version":"1.0.0"} |
Project conventions that must be reviewed before editing code.
app/ code (auto-activated via PreToolUse guard)conventions.md to review the current project coding rules.Read the conventions file in this skill directory:
Read: .agents/skills/project-conventions/conventions.md
Proceed with code edits after reviewing the conventions.