Menu
Create a GitHub issue for a feature, bug fix, or crash with all required TAOM sections
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
Root-cause native Bannerlord CTDs (AccessViolation in TaleWorlds.Native.dll) via Event Log offsets, offline disassembly, and live debugger forensics. No symbols needed.
Dispatch an independent Codex verification job directly via `codex exec` Bash call, then retrieve and present results
Inspect all changed files, group by logical concern, and guide atomic per-concern commits following TAOM's 50/72 rule and commit trailer convention.
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.
Launch parallel deep-dive agents to review completed work for quality, standards, compatibility, completeness, and cross-system data flow
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.
| name | issue |
| description | Create a GitHub issue for a feature, bug fix, or crash with all required TAOM sections |
| argument-hint | [bug|feature|crash] [brief description] |
Create a GitHub issue following TAOM's mandatory issue format.
$ARGUMENTSDetermine from $ARGUMENTS whether this is a bug/crash fix or a feature.
Run this command after filling in the template:
gh issue create \
--title "[one-line description of the bug/crash]" \
--label "bug" \
--body "$(cat <<'EOF'
## Problem
[Exact error message or symptom. Stack trace if available. Steps to reproduce.]
## Analysis
[Root cause. What was examined. Why it happened. What TaleWorlds internals were involved.]
## Solution
[What was changed. Why this approach was chosen over alternatives.]
## Files Changed
| File | Change |
|------|--------|
| `path/to/file.cs` | One-line description |
## Testing
[How the fix was verified. Unit tests added/updated. Manual testing steps.]
EOF
)"
gh issue create \
--title "[one-line description of the feature]" \
--label "feature" \
--body "$(cat <<'EOF'
## Motivation
[Why this feature exists. What problem it solves. Specific examples.]
## Design
[Architecture decisions. Extension points used (GameModel, Harmony, CampaignBehavior). Alternatives considered.]
## Implementation
[Key files. Patterns used. Configuration format. IoC registration.]
## Testing
[Test coverage summary. How to verify it works in-game.]
EOF
)"
$ARGUMENTSgh issue create commandClose the issue when done:
gh issue close <number> --comment "Resolved in [commit hash]. [One-sentence summary of what was done.]"