pkuppens/quality-gate

Quality Gate

Enforces code quality before commits and PRs. Runs the minimum required checks for the repo's toolchain.

When to use

• Before every git commit
• Before opening a PR
• After implementation to catch style and correctness issues early

Standard checks

Run these in order (fail fast):

# 1. Lint — catch style and logic issues
uv run ruff check .

# 2. Format — enforce consistent style
uv run ruff format --check .

# 3. Type check (if configured)
uv run ty        # Astral type checker; or: uv run pyright

# 4. Tests
uv run pytest

# 5. Pre-commit (runs all hooks)
pre-commit run --all-files

Per-check sub-skills

When these sub-skills are created, invoke them for per-check focus. Until then, run the commands in Standard checks above.

| Sub-skill | Tool | When | |-----------|------|------| | quality-gate-lint | ruff check | Every commit | | quality-gate-format | ruff format | Every commit | | quality-gate-type | ty / pyright | Before PR | | quality-gate-security | ruff check (S rules) / bandit / npm audit | Before PR / CI |

Fix before commit — not after

• Fix lint and format errors immediately; do not --no-verify.
• If a pre-commit hook blocks a commit, investigate the root cause — do not bypass.
• If a check is not configured for this repo, skip it and note the gap.

OpenClaw projects

When the repo is an OpenClaw project (openclaw config, gateway, or agent code), run openclaw-security as a mandatory check:

openclaw security audit --deep
openclaw security audit --fix

Both must pass before integration-commit. Report in Quality Gate Results.

Repo-specific toolchain

Check the repo's pyproject.toml for:

• [tool.ruff] — line length, selected rules
• [tool.ty] or [tool.pyright] — type checking configuration
• .pre-commit-config.yaml — active hooks

Output

Report pass/fail per check:

## Quality Gate Results

- [x] ruff check — clean
- [x] ruff format --check — clean
- [ ] ty — 2 errors (see below)
- [x] pytest — 42 passed, 0 failed

List errors with file and line reference for any failures.

Integration

• Run after implementation-construction.
• Must pass before integration-commit.
• Use verification-before-completion before claiming work is ready.