Every Three Cubes repo runs the same quality check and the same CI and deploy steps. We used to hand-copy those into each repo, and the copies drifted apart. Now there is one shared quality check and one shared set of CI steps, and every repo uses them. You run the check on your laptop and get the exact result CI will give — no "works on my machine", and one fix to the shared check improves every repo at once.

Used today by tc-agent-zone · kairix · kata.

• Green merges itself. When your PR's checks pass, it merges on its own. Routine work does not wait for a human reviewer.
• Red is never bypassed. If checks fail, you fix the change. You do not force it in — force-merging over a red check is exactly what breaks the main branch.
• Only changes to the checks themselves need a human. Changing the quality check or the CI config (the files that define how everything is checked) requires one human approval. This stops anyone — person or agent — from quietly weakening the check that protects every repo.
• Agents work under a bot identity. Agents open PRs as the three-cubes-agent GitHub App, so authorship is clean and the work can be reviewed when needed.

• New here / want the overview? Read STANDARDS.md — the one canonical index that links to everything authoritative.
• Setting up or building a repo? Add the quality check and lock it to a version: put three-cubes-fitness @ git+https://github.com/three-cubes/tc-fitness.git@vX in your deps and a [tool.tc_fitness] block in pyproject.toml. Then add the CI caller: uses: three-cubes/tc-pipelines/.github/workflows/python-quality-gate.yml@v1. See tc-pipelines/docs/MIGRATION.md. Always lock to a tag — never @main.
• An agent? Each repo's CLAUDE.md / AGENTS.md points you at STANDARDS.md before you touch CI, the quality check, or governance. Read it first; improve the canonical standard instead of forking your own.

1. Make your change on a branch.

2. Run the check locally the same way CI does. Install the full dev environment, then run both commands and get them green before you push:

   uv sync --all-extras --all-groups
   uv run pre-commit run --all-files
   uv run tc-fitness run

3. If it is green locally but red in CI, that is a bug in the local setup — fix the setup, do not force the merge.

4. If you changed an input to a generated file (for example .github/CODEOWNERS), regenerate the generated file and commit it in the same change.

5. Open a PR. Green merges itself. If it touches a file that defines the checks or CI, one human approves first.