Menú
Create a GitHub issue for a feature, bug fix, or crash with all required DOTS sections
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.
Basado en la clasificación ocupacional SOC
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 | issue |
| description | Create a GitHub issue for a feature, bug fix, or crash with all required DOTS sections |
| argument-hint | [bug|feature|crash] [brief description] |
Create a GitHub issue following DOTS'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.]"