Menu
Verify DOTS's Harmony patch, GameModel, and reflection bindings against the installed Bannerlord engine and refresh the committed API snapshot. Use after an engine update or patch change.
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
Author a culture's armor items and swap troop equipment rosters via the generator + validation pipeline. Use when adding/revamping armor. Enforces the canonical-folder + cover-attribute rules.
Give DOTS lords lore-driven skill values and traits via the DOTS SkillSet system. Use when a canonical lord has wrong stats or a culture roster needs a balance pass.
Author or revamp a DOTS culture's armor set, troop tree, and recruitment wiring end-to-end. Use for new cultures or troop-tree revamps. Follows docs/ai-includes/new-culture-authoring.md.
Use when reviewing an external repo or article to adopt practices into DOTS — security-vet first, map novel vs duplicative, port (never install), review, commit your changes.
Structured 4-phase self-debug for failing agent runs (looping, drifting, burning tokens). Capture, diagnose, contained recovery, report. Complements /investigate (which is for code bugs); this skill is for harness/agent failures.
Incrementally fix dotnet build errors with minimal diffs, one error at a time
| name | verify-bindings |
| description | Verify DOTS's Harmony patch, GameModel, and reflection bindings against the installed Bannerlord engine and refresh the committed API snapshot. Use after an engine update or patch change. |
| argument-hint | ["check|refresh|full"] |
Re-verify that DOTS's engine touchpoints still bind against the installed Bannerlord version, and keep the committed v1.4.5 signature snapshot in sync. This is the standing, offline form of the migration S6 smoke-test gate.
Full background: docs/reference/taleworlds-api-snapshot/README.md.
Dots*Model GameModel, or a string-name reflection site against an engine member.$ARGUMENTS = check → run the binding gate only (Step 1).$ARGUMENTS = refresh → regenerate the snapshot only (Step 3).$ARGUMENTS = full or empty → all steps.BANNERLORD_GAME_DIR (or BANNERLORD_OVERRIDE_DIR) must point at the install — the gate loads the SandBox/CustomBattle/StoryMode module DLLs from there. If unset, the gate self-reports Assert.Inconclusive (it does not falsely pass). This is an environment fact to report, not fix (see .claude/rules/environment-failures.md).
dotnet test DOTS.Tests/DOTS.Tests.csproj -p:DisableModuleCopy=true --filter "TestCategory=BindingVerification"
Three test classes under DOTS.Tests/Migration/:
HarmonyPatchBindingTests — every [HarmonyPatch] / TargetMethod target resolves as Harmony resolves it.GameModelOverrideBindingTests — every Dots*Model is registered in SubModule.cs, overrides ≥1 base virtual, and doesn't shadow a base virtual without override.ReflectionSiteBindingTests — each catalogued auxiliary reflection member resolves.A red gate is a real finding — one of three classes. Fix at the source, do not silence the test:
| Failure message | Root cause | Fix |
|---|---|---|
AmbiguousMatchException on a patch | name-only [HarmonyPatch] on a method overloaded anywhere in the type hierarchy | pin argument types: [HarmonyPatch(typeof(X), "M", new[] { typeof(...) })] (the documented HarmonyLib way) |
target/member did not resolve / not found | engine renamed/moved/removed the member in this version | /research the new signature, update the patch / adapter / GameModel; if a reflection site, update both reflection-sites.md and the [DataRow] |
GameModel never AddModel'd | a Dots*Model compiles but isn't registered | add campaignStarter.AddModel(new DotsXModel(...)) in Main/SubModule.cs |
If the fix needs an unknown TaleWorlds signature, hand off to /research first. If it's a deeper "why did this break" question, use /investigate.
pwsh tools/snapshot_api_surface.ps1
Regenerates docs/reference/taleworlds-api-snapshot/{gamemodel-bases,patch-targets}.md from the installed DLLs (auto-derives the type list from DOTS.dll). Then prove reproducibility:
pwsh tools/snapshot_api_surface.ps1 -Check # exit 0 = committed files reproduce
Add a row to reflection-sites.md Category B and a matching [DataRow] in ReflectionSiteBindingTests.cs. Runtime-dynamic sites (instance.GetType()) go in Category C (not gated) and onto the punch-list instead.
The gate is offline-only. Patch application, prefab visual order, ruler equipment, alliance behaviour, naval safety, and dynamic-reflection CC flow need a running game — itemized in docs/migration/s6-runtime-punchlist.md. Surface these to the user; do not claim them verified from a green gate.
Report: gate result (pass/fail with the per-finding class for any failure), whether the snapshot reproduced (-Check exit code), and any open punch-list items the change implicates. Update docs/migration/TRACKING.md and CHANGELOG.md if bindings were fixed.