oblt-aw / rules

---
description: GOLD — mandatory local pre-commit (actionlint/ruff/mypy/…) before every commit or push.
alwaysApply: true
---

# GOLD rule — pre-commit before commit / push

**Highest-priority CI hygiene rule for this repository.** It overrides the urge to “pytest passed, ship it.”

## Non-negotiable

Before **any** of these:

- `git commit` (when the agent is creating the commit)
- `git push`
- `gh pr create` / updating a PR with new commits

you **must** run and pass:

```bash
pre-commit run --files <all-paths-changed-in-this-change-set>
```

Use the exact touched paths (new, modified, deleted→related). That matches CI’s **Pre-commit** job (yamllint, **actionlint**/shellcheck-in-workflows, ruff, ruff format, **mypy**, license headers, yaml/json hygiene).

If many files changed, `pre-commit run --all-files` is acceptable and stricter.

## Forbidden shortcuts

- Treating **pytest alone** as authorization to commit or push
- Skipping **actionlint** because “the YAML looks fine”
- Skipping **mypy** because “types look fine”
- Pushing after a known red Pre-commit “to fix in a follow-up”
- Committing/pushing first, then running pre-commit only after CI fails

## Mandatory report

When offering or performing commit/push/PR, **state in one line** that pre-commit passed on the touched files (hook list not required). If it failed, **stop**, paste the failing hook output, fix, re-run, then proceed.

## Install (humans and agents)

```bash
pre-commit install --hook-type pre-commit --hook-type pre-push
```

`pre-push` is configured in [.pre-commit-config.yaml](../../.pre-commit-config.yaml) so a bare `git push` also runs the gate after install.