Menu
Run the full project verification gate. Use before committing or when user says "verify", "check", or "run checks".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | verify |
| description | Run the full project verification gate. Use before committing or when user says "verify", "check", or "run checks". |
| disable-model-invocation | true |
git branch --show-currentgit status --shortRun the full verification gate. Execute each step and report pass/fail:
make lint (Ruff — F401, F403, F405, F821, F841)make lint-frontend (ESLint — max-warnings=0)make tsc (npx tsc --noEmit)make prisma-validate (schema consistency)make git-integrity (exclude poisoning check)make test (pytest -q --tb=short)VERIFICATION GATE
- Python lint: [PASS/FAIL]
- Frontend lint: [PASS/FAIL]
- TypeScript check: [PASS/FAIL]
- Prisma validate: [PASS/FAIL]
- Git integrity: [PASS/FAIL]
- Python tests: [PASS/FAIL]
RESULT: [ALL PASS / X FAILURES]
If any step fails, show the error output and suggest a fix. Do NOT proceed to commit if any step fails.
Run ML training pipeline steps (specialists, core, evaluation, forecasts, monte-carlo). Use when user asks to run or re-run any part of the prediction pipeline.
Use when the user says "review my code", "check my changes", "run a review", "anything I should fix before merging", or wants a pre-commit or pre-PR quality check on local changes. Runs both CodeScene (structural code health) and cubic (AI semantic review) then surfaces all issues grouped by severity.
Use when the user asks about codebase architecture, "how does X work", system design, onboarding to a project, or needs context about how parts of the codebase connect. Queries cubic's AI Wiki for the current repository to provide architectural context.
Use when the user says "check cubic comments", "cubic issues", "cubic feedback", "cubic code review", "fix issues", "address review", or is working on a pull request branch with open review comments. Fetches all PR issues from cubic, investigates each one, and reports back which are worth fixing before taking action.
Use when the user is writing code, reviewing code, asking about code quality standards, or wondering "what does this team care about in reviews". Pulls team-specific review learnings from cubic to apply the team's coding conventions and review preferences.