Code Change Verification
Overview
Ensure work is only marked complete after formatting, linting, type checking, and tests pass. Use this skill when changes affect runtime code, tests, or build/test configuration. You can skip it for docs-only or repository metadata unless a user asks for the full stack.
Quick start
- •Keep this skill at
./.codex/skills/code-change-verificationso it loads automatically for the repository. - •macOS/Linux:
bash .codex/skills/code-change-verification/scripts/run.sh. - •Windows:
powershell -ExecutionPolicy Bypass -File .codex/skills/code-change-verification/scripts/run.ps1. - •If any command fails, fix the issue, rerun the script, and report the failing output.
- •Confirm completion only when all commands succeed with no remaining issues.
Manual workflow
- •If dependencies are not installed or have changed, run
make syncfirst to install dev requirements viauv. - •Run from the repository root in this order:
make format,make lint,make mypy,make tests. - •Do not skip steps; stop and fix issues immediately when a command fails.
- •Re-run the full stack after applying fixes so the commands execute in the required order.
Resources
scripts/run.sh
- •Executes the full verification sequence with fail-fast semantics from the repository root. Prefer this entry point to ensure the required commands run in the correct order.
scripts/run.ps1
- •Windows-friendly wrapper that runs the same verification sequence with fail-fast semantics. Use from PowerShell with execution policy bypass if required by your environment.