القائمة
Run lot gate checks — typecheck, lint, and scoped tests for current lot
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | lot-gate |
| description | Run lot gate checks — typecheck, lint, and scoped tests for current lot |
| paths | **/BRANCH.md |
| allowed-tools | Read Bash Grep |
Workflow skill to run the standard lot gate sequence for the current lot in BRANCH.md.
Read BRANCH.md Parse the current lot and its gate checklist. Identify:
ENV=<test|e2e>-<branch-slug>)Typecheck Run typecheck for in-scope components:
make typecheck-api ENV=<branch-env>
make typecheck-ui ENV=<branch-env>
Only run for components that have changes in this lot.
Lint Run lint for in-scope components:
make lint-api ENV=<branch-env>
make lint-ui ENV=<branch-env>
Only run for components that have changes in this lot.
Scoped tests Run each test category listed in the lot gate checklist:
make test-api SCOPE=<test-file> ENV=test-<branch-slug>make test-ui SCOPE=<test-file> ENV=testmake test-e2e E2E_SPEC=<test-file> API_PORT=<port> UI_PORT=<port> MAILDEV_UI_PORT=<port> ENV=e2e-<branch-slug>
Run scoped tests first (individual files), then the full sub-lot gate command.Report pass/fail For each gate item, report:
Update BRANCH.md checkboxes
Mark each completed gate item with [x] in BRANCH.md.
For failures, leave [ ] and add a blocked feedback loop entry.
ENV=dev — afterEach hooks purge real dataENV as the last argument to makeAPI_PORT, UI_PORT, MAILDEV_UI_PORTUse when bringing the harness method to a NEW or non-sentropic repo — maps the repo's conventions into a harness profile so the same scope/branch/verify kernel applies anywhere.
Use before any creative/design work (a feature, a package, an evolution) — explores intent and design via the spec-ladder with multi-peer adversarial review BEFORE implementation.
Use on any bug, test failure, or unexpected behaviour BEFORE proposing a fix — runs the generic evidence-first root-cause loop.
Use when you have a spec/decisions and need an executable plan — writes a lot-based BRANCH.md from the template and completes with track for realization state.
Use when completing a feature, a design step, or before merging — runs a ≥2-peer consensus review and reconciles the findings, instead of a single rubber-stamp pass.
Use when adding or evolving tests for a feature/bugfix — applies the sentropic test-pyramid, scoped-test loop, environment isolation, and AI-flaky policy.