code-quality

Run ruff, pyright, and pytest coverage checks for Python projects.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/nullhack/pytest-beehave --skill code-quality-nullhack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-quality
Source: https://github.com/nullhack/pytest-beehave/tree/main/.opencode/skills/code-quality
Command: npx skills add https://github.com/nullhack/pytest-beehave --skill code-quality-nullhack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code quality for Python projects is hard to maintain; this Skill automates linting, type checks, and test verification to catch issues early.

Core Features & Use Cases

  • Linting and formatting with ruff.
  • Static type checking with pyright.
  • Test coverage verification with pytest.
  • Quick health checks before PR or release.

Quick Start

Run the four verification steps to lint, type-check, test with coverage, and verify the app starts.

Frequently Asked Questions about code-quality

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

FAQPage Schema
How do I automate Python code quality checks in a CI pipeline?

Automate Python code quality checks by running linting, static type checks, and test coverage verification using ruff, pyright, and pytest. These tools execute via uv run task commands to ensure consistency before merging or releasing code.

What does static type checking with pyright catch in a Python project?

Static type checking with pyright catches type inconsistencies and errors in Python code before runtime. It runs alongside ruff for linting and pytest for coverage verification to enforce overall code quality.

Do I need to install ruff and pyright before running these quality checks?

Yes, you need ruff, pyright, and pytest with coverage configured and accessible in your environment. The automation uses uv run task commands to perform each verification step with these specific dependencies.

What's the best way to run a quick health check before a Python PR?

Run a quick health check before a PR by executing four verification steps to lint, type-check, test with coverage, and verify the app starts. This ensures code quality and consistency before merging.

Can I use this to enforce linting and formatting with ruff in pre-commit hooks?

Yes, you can enforce linting and formatting with ruff in pre-commit checks. The automation applies to development workflows and pre-commit checks to catch issues early before merging or releasing.