research

Estrellas2

Forks1

Actualizado26 de marzo de 2026 a las 09:47

Decompile and analyze TaleWorlds classes before implementing or fixing. Use when touching Harmony patches, adapters, GameModels, or investigating bugs.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Fuente

haterade22

haterade22/TAOM

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	research
description	Decompile and analyze TaleWorlds classes before implementing or fixing. Use when touching Harmony patches, adapters, GameModels, or investigating bugs.
argument-hint	["ClassName or DLL.ClassName"]

TaleWorlds Research Skill

Follow the TaleWorlds Research Protocol from @docs/ai-includes/taleworlds-research-guide.md

Target

Decompile and analyze: $ARGUMENTS

Workflow

Identify the DLL — Determine which assembly contains the target class:
- TaleWorlds.CampaignSystem.dll — Campaign logic, kingdom decisions, diplomacy
- TaleWorlds.CampaignSystem.ViewModelCollection.dll — UI ViewModels
- TaleWorlds.Core.dll — Core game types
- TaleWorlds.MountAndBlade.dll — Battle/mission logic
- TaleWorlds.Library.dll — Base types, PropertyOwner
- SandBox.dll / SandBox.ViewModelCollection.dll — Sandbox-specific logic

Decompile the class — Use the ILSpy MCP server (preferred) or fall back to ilspycmd:

# Preferred: ILSpy MCP (configured in .vscode/mcp.json)
mcp__ilspy__decompile_type("E:\Steam\steamapps\common\Mount & Blade II Bannerlord\bin\Win64_Shipping_Client\<DLL>", "TaleWorlds.<Namespace>.<ClassName>")

# Fallback: CLI
ilspycmd "%BANNERLORD_GAME_DIR%\bin\Win64_Shipping_Client\<DLL>" -t "TaleWorlds.<Namespace>.<ClassName>"

Analyze the decompiled output:
- Method signatures (parameters, return types, access modifiers)
- Virtual vs sealed vs static methods
- Property getters/setters and computed properties
- Null handling patterns (TextObject.Empty vs null)
- Collection types and modification safety
- Event timing and state change ordering
Document findings — Summarize:
- Key methods and their signatures
- Properties (read-only vs read-write)
- Nested sealed types that need adapter wrapping
- Important null/edge case behavior
- Any v1.3.12-specific changes observed
Provide recommendations for how to safely integrate with the analyzed class.

Más de este repositorio

mismo repositorio

native-crash-triage

haterade22/TAOM

Root-cause native Bannerlord CTDs (AccessViolation in TaleWorlds.Native.dll) via Event Log offsets, offline disassembly, and live debugger forensics. No symbols needed.

2026-07-242

codex-verify

haterade22/TAOM

Dispatch an independent Codex verification job directly via `codex exec` Bash call, then retrieve and present results

2026-07-222

commit-split

haterade22/TAOM

Inspect all changed files, group by logical concern, and guide atomic per-concern commits following TAOM's 50/72 rule and commit trailer convention.

2026-07-222

context-restore

haterade22/TAOM

Load a snapshot saved by /context-save and present it so this session can pick up where the last one left off without re-deriving decisions.

2026-07-222

deep-review

haterade22/TAOM

Launch parallel deep-dive agents to review completed work for quality, standards, compatibility, completeness, and cross-system data flow

2026-07-222

engine-bump

haterade22/TAOM

Respond to a Bannerlord engine update (Steam force-bump or deliberate migration) — preserve the decompile baseline, regen, diff, re-verify bindings and creature data, control-battle.

2026-07-222

name	research
description	Decompile and analyze TaleWorlds classes before implementing or fixing. Use when touching Harmony patches, adapters, GameModels, or investigating bugs.
argument-hint	["ClassName or DLL.ClassName"]

TaleWorlds Research Skill

Follow the TaleWorlds Research Protocol from @docs/ai-includes/taleworlds-research-guide.md

Target

Decompile and analyze: $ARGUMENTS

Workflow

Identify the DLL — Determine which assembly contains the target class:
- TaleWorlds.CampaignSystem.dll — Campaign logic, kingdom decisions, diplomacy
- TaleWorlds.CampaignSystem.ViewModelCollection.dll — UI ViewModels
- TaleWorlds.Core.dll — Core game types
- TaleWorlds.MountAndBlade.dll — Battle/mission logic
- TaleWorlds.Library.dll — Base types, PropertyOwner
- SandBox.dll / SandBox.ViewModelCollection.dll — Sandbox-specific logic

Decompile the class — Use the ILSpy MCP server (preferred) or fall back to ilspycmd:

# Preferred: ILSpy MCP (configured in .vscode/mcp.json)
mcp__ilspy__decompile_type("E:\Steam\steamapps\common\Mount & Blade II Bannerlord\bin\Win64_Shipping_Client\<DLL>", "TaleWorlds.<Namespace>.<ClassName>")

# Fallback: CLI
ilspycmd "%BANNERLORD_GAME_DIR%\bin\Win64_Shipping_Client\<DLL>" -t "TaleWorlds.<Namespace>.<ClassName>"

Analyze the decompiled output:
- Method signatures (parameters, return types, access modifiers)
- Virtual vs sealed vs static methods
- Property getters/setters and computed properties
- Null handling patterns (TextObject.Empty vs null)
- Collection types and modification safety
- Event timing and state change ordering
Document findings — Summarize:
- Key methods and their signatures
- Properties (read-only vs read-write)
- Nested sealed types that need adapter wrapping
- Important null/edge case behavior
- Any v1.3.12-specific changes observed
Provide recommendations for how to safely integrate with the analyzed class.