| name | codex-verify |
| description | Dispatch an independent Codex verification job for the current changes |
| argument-hint | [feature-name or file-path] |
Codex Independent Verification
Dispatch an independent Codex review. Codex reviews with no shared Claude context.
Target: $ARGUMENTS (if empty, verify all uncommitted changes).
Step 1: Identify Files to Review
- If
$ARGUMENTS provided: find files in Main/Features/$ARGUMENTS/ and LOTRAOM.Tests/Features/$ARGUMENTS/
- Otherwise:
git diff --name-only + git ls-files --others --exclude-standard
- Filter to
.cs files
Step 2: Dispatch Codex Review
/codex:rescue Review these C# files for the LOTRAOM Bannerlord mod:
FILES: [file list]
Focus on:
1. Adapter pattern violations (ADR-007) -- sealed TaleWorlds types in service classes
2. Thin entry point violations (ADR-002) -- entry points over 150 lines
3. Harmony patch targets -- verify method signatures match game DLLs
4. Test coverage gaps -- services without test files
5. GameModel override correctness -- inheriting Default*, calling base.Method()
6. No #region blocks (ADR-003)
7. No [Obsolete] without migration (ADR-004)
8. Culture lookups use ICultureMapper, never .Name.ToString()
Rate each finding: CRITICAL / HIGH / MEDIUM / LOW
Format: [SEVERITY] file.cs:line -- description -- remediation
Step 3: Monitor Background Job
Use the Monitor tool to stream Codex progress. Check manually: /codex:status
Step 4: Retrieve and Display Results
/codex:result
Format as severity-grouped report with VERDICT: CLEAN / ISSUES FOUND.