compat-check
Check mod compatibility against a new Bannerlord version by reviewing patch targets and GameModel overrides
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Check mod compatibility against a new Bannerlord version by reviewing patch targets and GameModel overrides
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
Dispatch an independent Codex verification job for the current changes
Inspect all changed files, group by logical concern, and guide atomic per-concern commits
| name | compat-check |
| description | Check mod compatibility against a new Bannerlord version by reviewing patch targets and GameModel overrides |
| argument-hint | [new-version or path-to-decompiled] |
Check LOTRAOM compatibility against a new Bannerlord version.
Scan the codebase for:
grep -rn "HarmonyPatch" Main/ --include="*.cs" | grep -v "Test"
grep -rn ": Default" Main/Models/ --include="*.cs"
grep -rn "typeof(" Main/ --include="*.cs" | grep -i "taleworlds"
For each [HarmonyPatch] target:
For each GameModel inheriting Default*:
base.Method() calls are still validFor each typeof() or string-based reflection:
COMPATIBILITY REPORT: Bannerlord [version]
==========================================
BREAKING: N changes (must fix before update)
WARNING: N changes (may affect behavior)
SAFE: N targets verified compatible
[Grouped findings with file:line references]
For each BREAKING change, create a GitHub issue with remediation steps.