# Choruz Pre Push Checks > Use before pushing, marking ready for review, or claiming checks pass on a Choruz branch, to select the smallest tests and checks that cover the outgoing diff without reflexively running the full repository suite. - Skill: `inclusionai/choruz-pre-push-checks` (Agent Skill) - Install (CLI): `npx skillmds@latest add inclusionai/choruz-pre-push-checks` - Raw SKILL.md: https://api.skillmd.com/api/skills/inclusionai/choruz-pre-push-checks/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: inclusionai (https://skillmd.com/u/inclusionai) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/inclusionai/choruz-pre-push-checks --- # Choruz pre-push checks When loaded from a personal skills directory, resolve repository links from this skill's canonical `.agents/skills/choruz-pre-push-checks/` location in the active Choruz checkout, not from the installed copy. Run relevant local evidence once before a push. There are no git hooks in this repository; CI owns exhaustive coverage, and it runs only what the changed paths need. A red job that could have been caught locally costs a CI round trip and a reviewer's trust. ## Inspect the outgoing change 1. Confirm the checkout and branch. ```sh git status --short --branch git fetch -q origin main ``` 2. Print what CI will run for this diff and what to run first. The helper uses the workflow's own selector scripts, so its answer matches the pull request's `Detect changes` job: ```sh bash .agents/skills/choruz-pr/pr-plan.sh # against origin/main bash .agents/skills/choruz-pr/pr-plan.sh # for a stacked branch ``` ## Select relevant evidence Every behaviour change needs the narrowest available test that would fail for its regression; add broader checks only for surfaces the diff reaches. When the change adds or changes a resource-owning, parallel, or asynchronous test, apply [choruz-ci-test-reliability](../choruz-ci-test-reliability/SKILL.md) first. First map the outgoing scope to the policy's [behaviour acceptance evidence](../../../docs/testing/pr-test-policy.md#behaviour-acceptance-evidence). Inspect the selected assertions against that contract. `pr-plan.sh` and `vitest related` discover candidate checks, not proof of coverage: configuration, dynamic loading, subprocesses, cross-device dispatch and built artifacts can cross boundaries the import graph does not express. Explicitly select their owning scenarios and add missing tests; an empty selection is not passing evidence. Do not widen every change to the full suite or add `--passWithNoTests` to hide a missing owner. - **Rust crate or service:** `cargo fmt --check`, then `cargo clippy -p --all-targets -- -D warnings` and `cargo test -p ` for the crate and its dependents (`pr-plan.sh` lists them). Integration tests that need PostgreSQL use `infra/host/setup_test_database.sh`. - **Web source under `apps/web`:** `pnpm --dir apps/web exec vitest related --run ` (the whole suite, `pnpm web:test`, only when the harness or a shared config changed), then `pnpm web:check`. Run `pnpm web:build` when `next.config`, `app/` routing, or a dependency changed. - **User-visible flow crossing server or runtime boundaries:** the e2e spec that owns it, through the host stack: `bash infra/host/web_e2e.sh tests/e2e/.spec.ts`. A UI-only claim may use the policy's isolated component evidence. Use `--repeat-each=3` when repairing a flake; repetition does not replace a deterministic assertion or negative control. - **Migration or `crates/choruz-application` data path:** the DB smoke, `pnpm db:migration:smoke`, and the API smoke, `pnpm api:smoke`. An applied migration is checksum-frozen (`scripts/historical-migrations.sha256`): never edit one, add a successor. - **Agent Note, `AGENTS.md`, skill:** `python3 scripts/verify_agent_notes.py` and `python3 -m unittest discover scripts/tests`. - **CI workflow or selector script:** `python3 -m unittest discover .github/scripts/tests` and a YAML parse of `ci.yml`; the pull request itself runs the full suite once, by design. - **Contracts (`openapi/`):** `cargo test -p choruz-api-gateway contracts` (the spec must list every registered route and nothing else). - **Bridge, remote-control gateway, ops scripts:** their build or lint (`pnpm --dir services/choruz-bridge build`, the gateway checks in `ci.yml`, `pnpm ops:check`). Do not repeat a passing check merely because a commit or push follows. Do not run `pnpm preflight:full` by default; it is for an irreducibly repository-wide change or for diagnosing CI. ## Handle failures If a relevant check fails, stop and fix or explain the blocker. Do not push and hope CI differs. "Flake" is not a root cause: a test that passes only when run alone is a defect in the test, and [choruz-ci-test-reliability](../choruz-ci-test-reliability/SKILL.md) owns the fix. Never skip, disable, or quarantine a test to get green. If a failure looks environment-specific, prove it: record the exact command, the failing test, and the platform-specific mismatch; confirm the non-platform evidence; prefer fixing the nondeterminism. ## Push procedure 1. Run the selected checks once. 2. Commit with a Conventional Commits message; no model names or session identifiers beyond the trailers this repository already uses. 3. Push normally. Rewriting history is allowed only on a branch you created and never on someone else's; use `--force-with-lease`, never raw `--force`. 4. Verify the remote ref matches local `HEAD`, then watch the pull request checks: `CI (linux) required` is the one that gates the merge. Report pending checks as pending. Inspect a failure before attributing it to the branch or the environment. If no check ever starts, read `mergeStateStatus` first: GitHub creates no `pull_request` run while a PR is conflicting, and resolving the conflict is the only fix. At handoff, record the tested revision or dirty scope and the owning scenario's outcome, not just the command's exit status. Keep deterministic fixture results, live Harness results and manual visual observations separate; follow the policy when required evidence is unavailable.