Menu
Run comprehensive build + test + git verification and produce a pass/fail report
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | verify |
| description | Run comprehensive build + test + git verification and produce a pass/fail report |
| argument-hint | ["quick|full"] |
Run comprehensive verification on current codebase state.
$ARGUMENTS = quick → Build only (Step 1)$ARGUMENTS = full or empty → All stepsdotnet build Main --no-restore 2>&1
If it fails, report errors and STOP (no point running tests on broken build).
dotnet test DOTS.Tests --no-build 2>&1
Report:
git diff --stat
git diff --staged --stat
git ls-files --others --exclude-standard
Report:
grep -rE 'TODO|FIXME' Main/ --include='*.cs' | wc -l
Report count.
Check if CHANGELOG.md has been modified (staged or unstaged):
git diff --name-only -- CHANGELOG.md
git diff --staged --name-only -- CHANGELOG.md
If C# or XML files changed but CHANGELOG not updated, flag it.
Produce a concise verification report:
VERIFICATION REPORT
===================
Build: [PASS/FAIL]
Tests: [X/Y passed, Z failed]
Uncommitted: [X files modified, Y staged, Z untracked]
TODOs: [X in Main/]
CHANGELOG: [Updated/NOT UPDATED]
Ready for commit: [YES/NO]
Issues:
1. ...
2. ...
This is a READ-ONLY assessment followed by build/test execution. Do not make any code changes. Only analyze and report.
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