Review

Purpose

Audit the current branch against the global style guide and run the final code review process.

Workflow

1. •Load the style guide

• •Read ~/.codex/docs/style-guide.md.
• •Build a written checklist of issues before proposing any changes.

1. •Scope the review

• •Use git status and git diff to identify the current branch changes.
• •Prioritize reviewing changed files; expand to related files if needed to confirm consistency.

1. •Inspect for style-guide violations

• •Check for unsafe TypeScript, duplication, non-idiomatic patterns, and React concerns.
• •Use rg to locate patterns when needed.

1. •Report findings

• •Provide a concise checklist of every issue found.
• •Include file paths (and line numbers when feasible) for each issue.
• •If no issues are found, say so explicitly.

1. •Final code review process

• •Run through the steps in ~/.codex/prompts/final-code-review.md before concluding.

1. •Write to shared context

• •Append a "## Style Guide Review" section to factory/context.md.
• •Summarize findings and include key file references.

1. •Next-step guidance

• •Suggest fixes, but do not modify files unless explicitly asked.

Output format

• •Start with a short summary sentence.
• •Then list issues as bullets with file references and rationale.
• •End with a small "Suggested fixes" section if issues exist.