check-quality

Run ruff, pyright, and pytest coverage checks to enforce quality gates.

11|2|Updated Apr 7, 2022
One-click install
npx skills add https://github.com/nullhack/temple8 --skill check-quality-nullhack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-quality
Source: https://github.com/nullhack/temple8/tree/main/.opencode/skills/check-quality
Command: npx skills add https://github.com/nullhack/temple8 --skill check-quality-nullhack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces the software quality gate by ensuring linting, static type checking, and test coverage are satisfied before handoff to the system-architect.

Core Features & Use Cases

  • Lint with ruff to catch style and correctness issues.
  • Static type checks with pyright to detect type errors early.
  • Test-coverage verification with pytest to ensure adequate test suites.
  • Gate handoff: prevents unverified code from advancing to the next stage.

Quick Start

Run all four checks and confirm they pass before signalling handoff.

Frequently Asked Questions about check-quality

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

FAQPage Schema
How do I enforce code quality checks before handing off code to an architect?

Automate the quality gate by running ruff for linting, pyright for static type checks, and pytest for coverage verification. It exits with a non-zero status on failures, ensuring only compliant code advances to the system architect during handoffs.

What does a software quality gate check during feature development handoffs?

A software quality gate checks for style and correctness issues using ruff, type errors using pyright, and adequate test suites using pytest with coverage. It prevents unverified code from advancing to the next stage, ensuring release readiness before handoff.

Can I use ruff and pyright together for pre-handoff linting and static type checks?

Yes, you can use ruff and pyright together to catch style, correctness, and type errors early. Running both alongside pytest coverage verification automates the quality gate to ensure release readiness before handing off code to the system architect.

Do I need pytest with coverage to verify test suites for release readiness?

Yes, pytest with coverage is required to verify adequate test suites for release readiness. The quality gate uses pytest to ensure test coverage is satisfied before code is handed off to the system architect, exiting with a non-zero status if checks fail.

Why does my code quality gate exit with a non-zero status during handoff?

The quality gate exits with a non-zero status when linting, static type checks, or test-coverage verification fail. This mechanism prevents unverified or non-compliant code from advancing to the next stage during feature development handoffs.