DOTS

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

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 DOTS's 50/72 rule and commit trailer convention.

Audit context window consumption across DOTS agents, skills, rules, MCP servers, and CLAUDE.md. Report token estimates, flag bloat, recommend trims.

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.

Snapshot current working context (git state, in-flight tasks, key decisions, modified files) so a future session or post-compact resumption can pick up without losing progress. Pair with /context-restore.

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

Regression-safe cleanup of AI-generated bloat in C# code. Deletion-first, requires green tests before starting.

Use when navigating or auditing the docs/ knowledge graph — explain a doc's links, find the path between two docs, or surface god nodes / bridges / orphans.

Decompile and cache TaleWorlds v1.3.15 types via `dots-src path <Type>`. Returns absolute path for grep/cat composition. Use before patching, overriding, or writing adapters.

Integrate a merge-ready branch into the trunk — fast-forward check, merge, regenerate backlinks, CHANGELOG, delete branch (local+remote), push with confirmation. DOTS trunk-based, not Git Flow.

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.

Create a GitHub issue for a feature, bug fix, or crash with all required DOTS sections

Compile source material from docs/raw/<topic>/ into a navigable wiki node at docs/research/<topic>.md. Use when source-material has accumulated and needs summarization with cross-refs to existing feature docs / RCAs / memory.

Autonomous doc-rot reduction loop modeled on karpathy/autoresearch's program.md pattern. Picks one stale-version ref / dead link / orphan / missing-doc at a time, fixes it, re-lints, commits if the metric improved, advances or resets. Runs until 0 findings or N stuck iterations.

Run the doc-health linter (tools/lint_docs.py) over docs/ and summarize dead links, stale version refs, orphan/missing feature docs. Use when auditing knowledge-base health or after large doc moves.

Propagate new player-facing text through DOTS's 12-language localization pipeline — wrap with {=KEY}, register the string, run the Claude translation tool, validate. Use after adding UI text or XSLT strings.

Scaffold a new Architecture Decision Record, auto-numbered from existing ADRs, with context pre-filled from recent git history and CHANGELOG.

Scaffold a new DOTS feature module with IoC, services, adapters, and tests following project conventions

Auto-detect what was built, write a Codex adversarial prompt, dispatch Codex directly via `codex exec`, then verify results when complete

Use when auditing DOTS's Claude Code config for security issues — committed secrets, over-broad permissions, hook exfiltration, MCP risk, hidden-unicode injection. Runs tools/audit_claude_config.py.

Orchestrate the mandatory completion sequence before merging a C# feature — /verify, /deep-review, fix findings, /review-codex, then close the issue and update docs + CHANGELOG.

Periodic quality audit of installed skills + agents. Quick scan (recently changed only) or full audit. Catches decay (broken cross-references, stale paths, bloated descriptions) before sessions silently degrade.

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.

Run comprehensive build + test + git verification and produce a pass/fail report