القائمة
Run comprehensive build + test + git verification and produce a pass/fail report
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف 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 TAOM.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.
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.