القائمة
Project-specific build/test/lint/typing commands for this repo. Read this skill at the start of any phase that runs validation (`stoker-work`, `stoker-fixup`, `stoker-rebase`).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Drive a single pre-selected task through stoker-work's TDD cycle and commit/push/PR/close it (or stuck-mark it on failure). Use when invoked from the implement-phase prompt — the host has already picked the task and checked out its branch.
The universal red/green/refactor TDD methodology building block — drives a unit of work through plan → failing test → minimal implementation → refactor → validation against this repo's project-mechanics. Use when invoked from `stoker-implement` (always delegates here for the dev cycle), from `stoker-fixup` or `stoker-rebase` when a finding or conflict warrants the full TDD discipline rather than an in-place apply-and-validate, or any time the user wants to drive a feature/bug-fix/refactor through plan → test → implement → validate.
Drive a single pre-selected task through stoker-work's TDD cycle and commit/push/PR/close it (or stuck-mark it on failure). Use when invoked from the implement-phase prompt — the host has already picked the task and checked out its branch.
The universal red/green/refactor TDD methodology building block — drives a unit of work through plan → failing test → minimal implementation → refactor → validation against this repo's project-mechanics. Use when invoked from `stoker-implement` (always delegates here for the dev cycle), from `stoker-fixup` or `stoker-rebase` when a finding or conflict warrants the full TDD discipline rather than an in-place apply-and-validate, or any time the user wants to drive a feature/bug-fix/refactor through plan → test → implement → validate.
Create or update a pull request with a Summary / Validation steps / References body, including `Closes
Apply a trusted blocking stoker-review's findings to one PR — read the latest review JSON from the PR, fix what you agree with, re-validate against this repo's project-mechanics, push, and post a follow-up comment for anything you skip. Use when invoked from the stoker fixup-phase prompt, or when the user asks to address a stoker review's findings on a PR — and you are working in a stoker-installed repo. Consumes project-mechanics (Phase 0.5 prelude) and MAY delegate to stoker-work.
| name | project-mechanics |
| description | Project-specific build/test/lint/typing commands for this repo. Read this skill at the start of any phase that runs validation (`stoker-work`, `stoker-fixup`, `stoker-rebase`). |
This file is the source of truth for how this repo runs tests, lint, and type-checking. Profile-shipped phase skills read it at the start of each phase and use the named commands verbatim.
Docverse is a uv-workspace monorepo with three components: the
server (src/docverse/, tests/), the client
(client/), and the Cloudflare worker (cloudflare-worker/,
Node/TypeScript). The named commands below target the primary
(server) package; see ## Monorepo selectors for per-package routing.
focused_test: uv run --only-group=nox nox -s test -- tests/path/to/file_test.py::test_namecomplete_test: run only the suite(s) for the package(s) you changed,
per ## Monorepo selectors — server change →
uv run --only-group=nox nox -s test;
client change → uv run --only-group=nox nox -s client_test; both
changed → run both. The full cross-package suite is not the
in-iteration gate (see ## Final validation).lint_touched: uv run --only-group=lint pre-commit run --files {files}lint_all: uv run --only-group=lint pre-commit run --all-filestyping: uv run --only-group=nox nox -s typingEnd-of-task validation runs complete_test + lint_all + typing
in that order. Run the gate in the foreground and wait for it to
finish — it may take a few minutes; keep going, don't background it.
complete_test is package-scoped: run only the suite(s) for the
package(s) you changed (see ## Monorepo selectors). The full
cross-package run (nox -s test client_test) and the multi-version
compat suites (client_test_compat, client_test_oldest) are CI's
responsibility, not the in-iteration gate — do not run them here.
Additional checks by component:
cloudflare-worker/): cd cloudflare-worker && npm run build && npm test (run npm ci first if dependencies aren't installed).uv run --only-group=nox nox -s deploy_worker_test.Scope test/lint commands to the package you changed:
src/docverse/, tests/, alembic/, noxfile.py): uv run --only-group=nox nox -s test -- tests/...client/): uv run --only-group=nox nox -s client_test -- client/tests/...cloudflare-worker/): cd cloudflare-worker && npm run build && npm testlint_all / typing above cover all components).