القائمة
Hard verification gate — no task is complete without proof it works (Next.js/Supabase stack)
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/CleanExpo/Unite-Group --skill verification-firstيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
استنادا إلى تصنيف SOC المهني
The authoritative environment-variable registry for the Unite-Group Nexus. Use whenever adding, reading, renaming, or debugging an env var or secret — new integration config, a `process.env.X` read, an auth/OAuth wiring, a cron secret, a "which variable holds this" question, or a "works locally but not in prod" symptom. Also use before pinning any variable name in code, and when reconciling the two credential planes (Vercel prod vs the local hermes fleet). Prevents the `APIFY_API_KEY` vs `APIFY_API_TOKEN` class of drift.
Create, verify, and promote Supabase schema changes via database branches. Every schema change/migration must be validated on a Supabase database branch before prod (see CLAUDE.md line 44).
Verify production Supabase schema before shipping code that touches it. Use BEFORE writing or reviewing ANY code that reads or writes a Supabase table in the Nexus — new queries, inserts, updates, CHECK-constrained values, RLS-dependent reads, cron data access — even one-line changes and even when the table "obviously" exists. Also use immediately when a query fails with "column does not exist", when inserts appear to succeed but produce no rows, or when generated TypeScript types disagree with runtime behaviour.
عرض SKILL.md
| name | verification-first |
| category | verification |
| version | 2.0.0 |
| description | Hard verification gate — no task is complete without proof it works (Next.js/Supabase stack) |
| author | Unite Group (ported from NodeJS-Starter-V1) |
| priority | 1 |
| auto_load | true |
| triggers | ["any_code_change","post-implementation","pre-commit"] |
| context | fork |
A task is NOT complete until verification passes. "Almost working" = broken.
No self-attestation. No assumed success. Evidence required.
Every code change MUST be verified before moving on:
When something fails:
Before attempting any fix:
The agent that wrote the code MUST NOT verify its own work.
Route to [[verification]] agent. No exceptions.
# TypeScript type check
pnpm run type-check
# Lint
pnpm run lint
# Unit tests (Vitest)
pnpm vitest run
# Full pipeline
pnpm run type-check && pnpm run lint && pnpm vitest run
# Health check (comprehensive)
.\scripts\health-check.ps1
Note:
turboCLI is NOT available globally — usepnpm runscripts directly.
Trigger: After every code generation
pnpm build)Trigger: Before git commit
Trigger: Feature additions, migrations
Trigger: Before any production deploy
All verification reports MUST use this format:
## Verification: [Task Description]
### Status: [PASS | FAIL | BLOCKED]
### Tier: [A | B | C | D]
### Results:
- type-check: [PASS/FAIL] — [error if failed]
- lint: [PASS/FAIL] — [error if failed]
- unit-tests: [PASS/FAIL] — [X/Y passed]
- build: [PASS/FAIL] — [error if failed]
- manual: [PASS/FAIL] — [what was checked]
### Evidence:
[Actual command output, test results, or screenshot path]
### Next Steps:
[If PASS → what's next]
[If FAIL → root cause + proposed fix]
Verification is automatically enforced by:
post-code.hook.md — Runs Tier A after code generationpre-commit.hook.md — Runs Tier B before git commitpre-deploy.hook.md — Runs Tier D before deploymentFor any user-facing output, also verify:
When verification fails:
Stacking fixes creates the same problem as never testing: you don't know which change broke what.