Menu
Dispatch an independent Codex verification job for the current changes
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Audit context window consumption across LOTRAOM agents, skills, rules, MCP servers, and CLAUDE.md. Report token estimates, flag bloat, recommend trims.
Hard-block Edit/Write outside a chosen directory. Use to scope-lock edits during a focused fix or refactor. Pair with /unfreeze to release.
Six-phase root-cause debugging for crashes, build failures, or "why is this broken" reports. Iron Law - no fixes without root cause. Auto-engages /freeze.
Release the directory edit lock set by /freeze. Edit and Write are unrestricted again. No-op if /freeze was never set.
Inspect all changed files, group by logical concern, and guide atomic per-concern commits
Check mod compatibility against a new Bannerlord version by reviewing patch targets and GameModel overrides
| name | codex-verify |
| description | Dispatch an independent Codex verification job for the current changes |
| argument-hint | [feature-name or file-path] |
Dispatch an independent Codex review. Codex reviews with no shared Claude context.
Target: $ARGUMENTS (if empty, verify all uncommitted changes).
$ARGUMENTS provided: find files in Main/Features/$ARGUMENTS/ and LOTRAOM.Tests/Features/$ARGUMENTS/git diff --name-only + git ls-files --others --exclude-standard.cs files/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
Use the Monitor tool to stream Codex progress. Check manually: /codex:status
/codex:result
Format as severity-grouped report with VERDICT: CLEAN / ISSUES FOUND.