quality-gate

Run lint, format, type checks, and security scans on every commit.

Updated Jan 5, 2025
One-click install
npx skills add https://github.com/pkuppens/pkuppens --skill quality-gate-pkuppens
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-gate
Source: https://github.com/pkuppens/pkuppens/tree/main/skills/quality-gate
Command: npx skills add https://github.com/pkuppens/pkuppens --skill quality-gate-pkuppens

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces code quality before commits and PRs by running the minimum required checks for the repo's toolchain, catching style and correctness issues early.

Core Features & Use Cases

  • Lint checks with ruff to catch style and logic issues.
  • Format checks to enforce consistent styling.
  • Type checking with ty / pyright to catch type errors.
  • Security scanning to identify vulnerabilities.
  • Pre-commit integration to automatically run checks before commits or PRs.

Quick Start

Run the quality-gate before every commit to ensure all checks pass.

Frequently Asked Questions about quality-gate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce code quality checks before a git commit?

You can enforce code quality before a git commit by integrating pre-commit hooks that automatically run lint, format, type, and security checks on every commit attempt.

What's the best way to automate lint and format checks on push?

Automating lint and format checks on push is best handled by pre-commit integration that runs tools like ruff check and ruff format to catch style and logic issues early.

Can I run type checks and security scans together before a PR?

Yes, you can run type checks and security scans together before a PR by configuring a pre-commit hook to execute tools like ty or pyright alongside security audit scripts.

Does pre-commit work with ruff for Python lint and format enforcement?

Pre-commit works with ruff for Python lint and format enforcement by running ruff check and ruff format as deterministic steps to validate code quality before commits.

Why should I run code quality checks locally instead of only in CI?

Running code quality checks locally via pre-commit catches style and correctness issues early before they reach CI, reducing PR iterations and keeping the repository's main branch stable.

What checks do I need for Python pre-commit hygiene in varying repo sizes?

For Python pre-commit hygiene across varying repo sizes, you need lint checks, format enforcement, type checks, and security scans to validate code quality before every commit.